It's so over for C(++).

It's so over for C(++).

POSIWID: The Purpose Of A System Is What It Does Shirt $21.68

Yakub: World's Greatest Dad Shirt $21.68

POSIWID: The Purpose Of A System Is What It Does Shirt $21.68

  1. 3 weeks ago
    Anonymous

    Time to ~destruct, Cnlies!

  2. 3 weeks ago
    Anonymous

    Is it called Rust Nation UK because it's a project associated with Soros's Progressive Nation networks?

    • 3 weeks ago
      Anonymous

      I wonder how productive their C teams are. Oh wait, Google doesn't use C for their products for some reason.

      You have to go back.

      • 3 weeks ago
        Anonymous

        what google products ? they don't produce shit.

    • 3 weeks ago
      Anonymous

      israeli looking Black person right there on the stage.

    • 3 weeks ago
      Anonymous

      There we go, the Cnile cant say anything about the language itself this time so he goes full /misc/ mode in cope.

  3. 3 weeks ago
    Anonymous

    Man.. Rust wouldn't even be that bad of a languge.. if it wouldn't be associated with politics obsessed losers. Maybe if they were to give the language to ISO, there wouldn't be as many annoying """people""".

    • 3 weeks ago
      Anonymous

      I hear the memes but all the Rust people on IQfy only talk technical stuff and are nice to each other and strangers.
      The community seems good, meanwhile C++ doesn't even have one... like anywhere. It's competitive autism and moronation.

      • 3 weeks ago
        Anonymous

        I mean having reasonable people on IQfy is nice and all, but what about the rest of the internet? That's where the problem lies.

      • 3 weeks ago
        Anonymous

        > when the IQfyg community is much nicer than the public community
        Just when I thought I had seen it all, troons truly are a plague.

      • 3 weeks ago
        Anonymous

        >meanwhile C++ doesn't even have one... like anywhere
        perhaps because they're busy writing useful shit
        I mean just the idea that a fricking programming language needs to have a "community" is pure mental illness
        literally familyless friendless discord-using terminally online gay-tier behavior

        • 3 weeks ago
          Anonymous

          >I mean just the idea that a fricking programming language needs to have a "community" is pure mental illness
          nocoder spotted

      • 3 weeks ago
        Anonymous

        >It's competitive autism and moronation.
        the superior one so

      • 3 weeks ago
        Anonymous

        I love rust, way more comfy than c++, but honestly it bugs me that every rust resource is like
        >omg rewrite the universe on rust!
        it feels like a cult so I just stay away. like

        >meanwhile C++ doesn't even have one... like anywhere
        perhaps because they're busy writing useful shit
        I mean just the idea that a fricking programming language needs to have a "community" is pure mental illness
        literally familyless friendless discord-using terminally online gay-tier behavior

        said who tf needs a "community" anyways? start a fricking family

      • 3 weeks ago
        Anonymous

        >are nice to each other and strangers.
        >in a bait thread clearly made by a seething troony doing what they do best: talk shit about C
        Not nice. Get over it. C is the winner.

      • 3 weeks ago
        Anonymous

        that's because C++ programmers talk about C++ at their work places because there are actually jobs for it.

        • 3 weeks ago
          Anonymous

          there are jobs for Rust as well, update your memes mr. nocoder it's not 2015 anymore

  4. 3 weeks ago
    Anonymous
    • 3 weeks ago
      Anonymous

      A lot of the standard is poison. But you don't have to use those parts if you don't want to.

    • 3 weeks ago
      Anonymous

      In Rust this is just

      • 3 weeks ago
        Anonymous

        What are the actual use cases of this?

        • 3 weeks ago
          Anonymous

          You can let the compiler know some invariant you know to be always true but which is impossible to express at type level. Like "This float is actually a ratio so it's always <= 1.0", or "this pointer is never null, I checked it two functions back". This allows the compiler to better optimize the code. Tbh it's a very fragile hack, it would be better if the type system was able to express these invariants so they would be enforced at compile time, but that would require dependent types like Idris.

          • 3 weeks ago
            Anonymous

            You can use newtypes in Rust to express properties of a type.
            So for example struct EMail(String); is a transparent wrapper for strings that are a valid email

        • 3 weeks ago
          Anonymous

          Assumes are super useful, people have been using them with compiler intrinsics forever.
          Use cases:
          >do some non-trivial pointer arithmetic with xor and shit. The compiler can't prove the resulting pointer is correctly aligned, but you can, so you tell it with an __assumed_aligned_ptr().
          >data sent to an embedded device. You know preconditions about that data, but the embedded compiler can't, and it doesn't have any error handling mechanism, so you can't just write a guard clause that throws. You use assume to inform the compiler of the preconditions.
          >in general, as a superior form of assert. Compile in debug mode with -fsanitize=assert. Now in release mode, the compiler doesn't have to generate the error handling paths.

          • 3 weeks ago
            Anonymous

            I meant -fsanitize=unreachable

        • 3 weeks ago
          Anonymous

          Here's an example with a nice long explanation that mentions the effect on the assembly: https://github.com/tokio-rs/tracing/blob/master/tracing-core/src/metadata.rs#L716
          (tl;dr: need to cast an integer to an enum, this is a no-op if you promise it's always in range, very hot function so worth optimizing. Possibly could've used transmute instead in this case but maybe that'd make it harder to be fully checked in debug builds?)
          In general it's used pretty rarely.

        • 3 weeks ago
          Anonymous

          Also, a case I encountered recently
          >user writes a function `scan` that scans a table to find a key, and returns early with the corresponding value
          >in his design, he knows the function is never called when the element is missing, so the function will always return from within the for loop
          >the compiler doesn't know that, and since `scan` returns an int, he has to end the function body with a return statement, so he just adds `return 0;` after the for loop
          >note that in this context the value 0 is nonsensical (used as a length argument in other functions that shouldn't take null lengths)
          >the compiler sees that final return and thinks "mhhhhh, seems like 0 is a likely return value here, let me optimize a special path with it"
          >starts generating a completely nonsensical optimization path that adds bloat and causes problem for no reasons
          Adding an unreachable before the return 0; solves the problem entirely.

          • 3 weeks ago
            Anonymous

            Putting a panic/abort there would solve most of the problem without UB, right? I assume it knows those should be cold paths
            Of course sometimes you still want to go the extra mile and tell the compiler to not even take the possibility into account

          • 3 weeks ago
            Anonymous

            Yeah, for most cases an abort is enough, but if it's a hot loop function, sometimes you'd rather tighten the code as much as possible.

    • 3 weeks ago
      Anonymous

      >write obviously incorrect program
      >complain the problem is in the language
      cope

  5. 3 weeks ago
    Anonymous

    >Rust
    >UK
    >Google
    >Go
    >Conference
    I won bullshit buzzword bingo!

    • 3 weeks ago
      Anonymous

      It's called having a job, commie.

  6. 3 weeks ago
    Anonymous

    le video

    >In the talk, Lars mentions that they often rely on self-reported anonymous data. But in this case, Google is large enough that teams have developed similar systems and/or literally re-written things, and so this claim comes from analyzing projects before and after these re-writes, so you’re comparing like teams and like projects. Timestamped: https://youtu.be/6mZRWFQRvmw?t=27012

    >Some additional context on these two specific claims:

    >Google found that porting Go to Rust "it takes about the same sized team about the same time to build it, so that's no loss of productivity" and "we do see some benefits from it, we see reduced memory usage [...] and we also see a decreased defect rate over time"

    >On re-writing C++ into Rust: "in every case, we've seen a decrease by more than 2x in the amount of effort required to both build the services written in Rust, as well as maintain and update those services. [...] C++ is very expensive for us to maintain."

    • 3 weeks ago
      Anonymous

      Do they have figures on ports from C++ to Go? I wonder if part of the effect might be because rewrites are just easier

    • 3 weeks ago
      Anonymous

      did they measure the impact on the project that the team members killing themselves have?

      • 3 weeks ago
        Anonymous

        > one joke

    • 3 weeks ago
      Anonymous

      Meanwhile the Rust team has been working on async networking libraries for the last decade and everything is still a complete mess. If they're so productive what's taking them so long? Go and C# async networking libraries have worked flawlessly for over 10 years.

  7. 3 weeks ago
    Anonymous

    >Rush and Go are easier to understand for dumb dev who should have never been programmers in the first place

    many such cases

    • 3 weeks ago
      Anonymous

      Don't Cniles whine that Rust's syntax, borrow checker and async are too complicated compared to C's down-to-machine simplicity?

      • 3 weeks ago
        Anonymous

        Well yes they do and it's true.
        That guy filed at shitposting.

      • 3 weeks ago
        Anonymous

        >if you take the hardy way you're more smart-er
        moron.

    • 3 weeks ago
      Anonymous

      Don't Cniles whine that Rust's syntax, borrow checker and async are too complicated compared to C's down-to-machine simplicity?

      It probably has a lot to do with the toolchain. Go and Rust make it easy to add libs, automate tests, etc. With C it's a fricking mess.

      • 3 weeks ago
        Anonymous

        that "mess" enables you to do whatever you want with whatever tools you want. C and C++ front load the effort which is only bad if you write toy projects

        • 3 weeks ago
          Anonymous

          > do whatever you want with whatever tools you want
          This is not a good thing, not for the price. C/C++ dependency management is is ass, this is why every C project ends up (poorly) implementing its own containers, parsers, error handling and other common shit.

        • 3 weeks ago
          Anonymous

          defer to

          >you can use bindgen for working with existing C and C++ and if you need to call Java shitware or be called by java shitware, you have weird libs like j4rs.
          you have never worked on interop in any language or for any project. bindgen can barely emit alignment and sizeof blobs, even worse than gintrospect, and trips balls the moment you're working with c++.

          >tokio_util provides most the abstractions to build working framed protocol clients
          let me get this straight
          >rust is beri good at io
          >rust is beri good at io, its better than jeetware
          >rust is beri good at io, just install tokio
          >rust is beri good at io, just install tokio and tokio utility
          >rust is beri good at io, just install tokio, tokio utility, and use fibers ("""greenthreads""" ****)
          >rust is beri good at io, just install tokio, tokio utility, use fibers, and dont use any other lib that doesnt use my preferred io library

          ****: the concept invented for single threaded interpreters and boomer database-devs who couldnt write anything but while (true) { accept(); spawnThread(SocketHandler, fd); } loops.

          that "mess" is good enough on its own. your half-assed tooling that only works on a subset of freetard c libraries for linux puts you a decade behind what c# was capable of with just marshelas. also fun: the .net runtime doesn't blow up in your face, because your system hasnt been updated in 2 months and now the core package responsible for the FFI annotations is out of date with inconsistent ABI/API breakages (some fricking how)

      • 3 weeks ago
        Anonymous

        I would guess it has something to do with the age and complexity of the project codebases. The c++ codes could easily date from the inception of the company and deal with the hyper complex infrastructure of google. The rust codes are still young by definition. Its easy to crank out klocs on a new project.

  8. 3 weeks ago
    Anonymous

    >twice as productive as nothing
    Interesting metric.

  9. 3 weeks ago
    Anonymous

    How? I use C++ and I find Rust code unreadable.

    • 3 weeks ago
      Anonymous

      Have you actually tried to learn the language?

      >if you take the hardy way you're more smart-er
      moron.

      > using a primitive language means you're smarter

      [...]
      It probably has a lot to do with the toolchain. Go and Rust make it easy to add libs, automate tests, etc. With C it's a fricking mess.

      I'm pretty sure Google has a decent C++ workflow/tooling, considering it's been their main backend language since the beginning and they've been investing in the Clang toolbox for decades.

      • 3 weeks ago
        Anonymous

        >I'm pretty sure Google has a decent C++ workflow/tooling, considering it's been their main backend language since the beginning and they've been investing in the Clang toolbox for decades.
        their main backend language has always been java anon.

      • 3 weeks ago
        Anonymous

        >Have you actually tried to learn the language?
        NTA, but that's where the problem lies.
        I don't know Fortran either but I can understand what a piece of code does jsut by looking at it. Same goes for Go, Java, Python and so on.

        Rust syntax is just fricking ugly.

        • 3 weeks ago
          Anonymous

          I refuse to believe you can't understand Rust but you can intuitively grasp this bullshit.

          • 3 weeks ago
            Anonymous

            The difference is, Java is a normal language with normal syntax, Rust is just objectively abnormal and ugly for the sake of trying to be different.

          • 3 weeks ago
            Anonymous

            Do you read the internals of tokio? So why are you reading the internals of Spring? First rule of any library: stick to the public API.

      • 3 weeks ago
        Anonymous

        > using a primitive language means you're smarter
        Unironically yes.

    • 3 weeks ago
      Anonymous

      It's so ugly it could be a modern art masterpiece.

  10. 3 weeks ago
    Anonymous

    Define "productive"

    • 3 weeks ago
      Anonymous

      As in "creating more value to stakeholders", the only KPI out there, unless you're a socialist.

      • 3 weeks ago
        Anonymous

        I'm wondering how they define it.

  11. 3 weeks ago
    Anonymous

    Lines of code per day per programmer.

  12. 3 weeks ago
    Anonymous

    Ok, C++ seniles take 50 longer, but Rustrannies live 60% less, so we win

    • 3 weeks ago
      Anonymous

      Rust invented lifetime management because troons kept destructing too early.

      • 3 weeks ago
        Anonymous

        Ok, C++ seniles take 50 longer, but Rustrannies live 60% less, so we win

        One joke.

        • 3 weeks ago
          Anonymous

          its a good one.

  13. 3 weeks ago
    Anonymous

    >that pic
    is it even arguably untrue?
    I did professional C++ and can confirm that my limited use of Rust so far has been 10x easier to be productive with.

    • 3 weeks ago
      Anonymous

      It's time to move on. Abandon boomers behind.

      • 3 weeks ago
        Anonymous

        I am a 30 year old boomer though.

  14. 3 weeks ago
    Anonymous

    What can I use it for besides osdev/iot? Any interesting libs? Sell me on rust and I might actually waste some time to learn it.

    • 3 weeks ago
      Anonymous

      idk. I use it for throwing messages and useless memory moving bullshit for manufacturing systems.
      you can basically do whatever you want.

      some mad lads made a sql server driver in rust called Tiberius, it works well.
      You'll probably have to write your own MQ protos though. Openwire, IBM MQ, etc shit is all pretty sparce and the only libs that exist are unmaintained C shitware or literal nonfree header/shared-object garbage.

      tokio_util provides most the abstractions to build working framed protocol clients. nom is similar to things like parsec, if you used that before. It's nice, but obviously the more niche you go, the more work you have to do. Personally I think it's worth it. Anything you make in Rust will shit on Java jeet or pyBlack person shitware by leagues and it's easier to work with than C++. you can use bindgen for working with existing C and C++ and if you need to call Java shitware or be called by java shitware, you have weird libs like j4rs.

      • 3 weeks ago
        Anonymous

        >you can use bindgen for working with existing C and C++ and if you need to call Java shitware or be called by java shitware, you have weird libs like j4rs.
        you have never worked on interop in any language or for any project. bindgen can barely emit alignment and sizeof blobs, even worse than gintrospect, and trips balls the moment you're working with c++.

        >tokio_util provides most the abstractions to build working framed protocol clients
        let me get this straight
        >rust is beri good at io
        >rust is beri good at io, its better than jeetware
        >rust is beri good at io, just install tokio
        >rust is beri good at io, just install tokio and tokio utility
        >rust is beri good at io, just install tokio, tokio utility, and use fibers ("""greenthreads""" ****)
        >rust is beri good at io, just install tokio, tokio utility, use fibers, and dont use any other lib that doesnt use my preferred io library

        ****: the concept invented for single threaded interpreters and boomer database-devs who couldnt write anything but while (true) { accept(); spawnThread(SocketHandler, fd); } loops.

        • 3 weeks ago
          Anonymous

          you're a fricking moron. enjoy your shit performance in your shitlang because you're too moronic to understand a work-stealing scheduler.

          • 3 weeks ago
            Anonymous

            Imagine thinking a third task scheduler on top of the operating systems scheduler is somehow more efficient, despite being definitionally another layer of execution abstraction. Fibers are for morons who couldn't get into using modern IO concepts, and so, the user-land developers of some UNIX systems and Windows decided to invent fibers - context switching for morons who cant into recursion or proper io polling. Everybody knew this architecture was moronic, henceforth no operating system has first class support for user-space task scheduling. This leaves us with the python, lua, and javascript homosexuals who need coruns in order to manage mutliplexing "threads" on a single thread. This isn't you downloading more cpu. This is you and your shitlangs being moronic in the form of switching between global states in userspace at the time of a blocking read/write, because that's all shitlang devs could come up with. Same with java-jeets who wanted to spawn a thread for each web request. Your entire existence is a cope in order to appeal to cniles who couldn't write programs more complicated than while (true) { int fd = accept(); spawnThread(ClientLoop, fd); }

          • 3 weeks ago
            Anonymous

            >Imagine thinking a third task scheduler on top of the operating systems scheduler is somehow more efficient
            it is.
            you don't know what you're talking about.
            please leave this thread.

          • 3 weeks ago
            Anonymous

            You cannot be faster than your processor, you moronic homosexual. Adding fibers does not make your spin loop or natively asynchronous io request go any faster. You have 8-32 threads; layering schedulers upon schedulers upon schedulers because morons want a simple blocking read/write API is not making your code any faster.

          • 3 weeks ago
            Anonymous

            >You cannot be faster than your processor, you moronic homosexual
            why are you so confidently moronic? I don't get it. If you have something useful to say, say it, but as far as I can tell, one sentence into any of your posts just shows you're a fricking moron not worth responding to.

            no one is talking about fibers you absolute shitbrained moron. Rust's abstraction has nothing to do with fibers. Tokio is a basic b***h workstealing executor that's common in many areas.

            some homosexuals are all in on thread-per-core and pinning tasks, and those exist in the Rust ecosystem as well: glommio, etc.

            now FRICK OFF

          • 3 weeks ago
            Anonymous

            >Tokio is a basic b***h workstealing executor that's common in many areas.
            tokios docs is becoming littered with "greenthreads" references, and a workstealing executor would only make my argument even more valid. your shitty task dispatcher to handle the syntactic sugar of blocking-but-not-actually functions is not faster than a fricking spin-loop or the OS handling the IO itself.

          • 3 weeks ago
            Anonymous

            >words words words
            I still haven't heard you type anything intelligent or interesting. you really have no clue what you're talking about or so far up your own on ass in some academic sense that no one does what you're delusional mind fuzz has dreamed up.

          • 3 weeks ago
            Anonymous

            It's not faster than a well written multicore epoll/io_uring even loop with work stealing (something which only 0.01% of C programmers a capable to produce), but it's not slower either, and infinitely easier to code without creating data races, memory or logical error.

          • 3 weeks ago
            Anonymous

            >tokios docs is becoming littered with "greenthreads" references
            What the frick kind of braindead logic is this? You haven't proven anything.

          • 3 weeks ago
            Anonymous

            >What the frick kind of braindead logic is this? You haven't proven anything.
            read the rest of my statement before shutting down, moron.

            It's not faster than a well written multicore epoll/io_uring even loop with work stealing (something which only 0.01% of C programmers a capable to produce), but it's not slower either, and infinitely easier to code without creating data races, memory or logical error.

            >It's not faster than a well written multicore epoll/io_uring even loop with work stealing (something which only 0.01% of C programmers a capable to produce), but it's not slower either, and infinitely easier to code without creating data races, memory or logical error.
            This, but I don't consider mastering OVERLAPPED io on NT and epolls on Linux a 0.01% thing. It just filters a lot of midwits. Case in point, this thread.

          • 3 weeks ago
            Anonymous

            Have you heard about epoll/io_uring? Have you tried using it in pure C? I have, it's a fricking unmaintainable mess. Async Rust is basically syntactic sugar over it, making it straightforward to write with little to no overhead. And Rust dominates the Web Framework Benchmarks, thanks to async Rust.

          • 3 weeks ago
            Anonymous

            >I have, it's a fricking unmaintainable mess
            That anon here. I have and I tried emailing a complaint to the moron who maintains it. He is not interested in making his dead-shit kernel spinner remotely on par with what Win9x and NT3 were capable of 2-3 decades ago. Funny thing is, ive seen my complaint echoed all across the internet (wikis, orangesite posters, etc). He thought he was cute by copying how PCIe/DMA devices work, but nobody told him about MSI-x interrupts, and so then he realized still needs that io_submit equivalent call to kickstart his shitty libuv-but-its-the-kernel-subsystem thing. His entire shtick was to scam benchmarks, by making IO appear as cheap as the copying of io operation structures, in a bid to compensate for the embarrassing lack of asynchronous IO in the Linux kernel. The thing about all this is, io_urling and io_submit still block all the god damn time, you just have to deal with it yourself (io_submit) in a thread pool, or let the kernel do it (iopissring). I would say the funniest thing about io_pissring is, the developer malds out at anybody criticising his shit with the same excuse, "JUST USE MY REFERENCE (not public domain) C LIBRARY."

          • 3 weeks ago
            Anonymous

            You cannot be faster than your processor, you moronic homosexual. Adding fibers does not make your spin loop or natively asynchronous io request go any faster. You have 8-32 threads; layering schedulers upon schedulers upon schedulers because morons want a simple blocking read/write API is not making your code any faster.

            Async coroutines made fibers obsolete, but the ((software industry)) sat on the concept for 30 years and didn't tell anyone it existed.

            Nobody asked for Rust and nobody is getting out of bed for it, so there must be some nefarious reason it's getting pushed on us.

          • 3 weeks ago
            Anonymous

            >Nobody asked for Rust and nobody is getting out of bed for it, so there must be some nefarious reason it's getting pushed on us.
            It's a meme at this point. Modern rust was effectively invented by Mozilla as a "replacement for C++ in the firefox codebase," yet they have rewritten exactly 0% of the codebase in rust. Being more specific, they rewrote the URL parser in rust, and now we have that scuffed implementation of webgpu the rust trannies are holding up at the next high level graphics api (its not. lmao). All this is to say rust has pretty much no adoption in the one god damn place it was invented for. Should you take a peek at the people behind it, not only do you find unhinged (literal) troony dom posting, you find them posting "books" (they're trying to be academic with md files) on how they fricked something up. Specifically, they try to explain how/why they implement a platform the way they did, just to oust themselves as being wholy incompetent, to the point where its clear they dont even understand the fundamentals of what theyre doing. [example snipped post too long.] I digress about their incompetence. The funniest thing that exposes this whole "you're a firefox language that didn't even replace flash or c++"-grift is, all their defenders use the exact same tactic: they go on reddit and spam "muh chromium cves." Don't get me wrong. Chromium security team is a joke, and indeed there's a lot of bad ivan/jeet code in Chrome, but that's neither here nor there. The point is rust trannies use their actual competitor, google chrome, as an excuse to shit on C++ as it exists in system programming and embedded applications, when in reality their shitlang doesnt even support/belong anywhere in anything past 2-year-old igay-devices and Windows 10 machines.

          • 3 weeks ago
            Anonymous

            ?

          • 3 weeks ago
            Anonymous

            Those numbers are fake and don't count.

          • 3 weeks ago
            Anonymous

            is stylo real?

          • 3 weeks ago
            Anonymous

            >Rust is only a tiny fraction of C, C++, the JavaScript frontend, and mere markup files for theming EACH, INDIVIDUALLY
            You've just proven my point. The rewrite in rust meme started by Moz devs for FireFox, and yet it didnt even make it to FireFox.

          • 3 weeks ago
            Anonymous

            mozilla FIRED the servo devs btw

          • 3 weeks ago
            Anonymous

            Rust was invented so that you could trust moronic pajeets to not commit broken exploitable garbage, and now chatgpt does a better job for free. Rust was DoA

          • 3 weeks ago
            Anonymous

            Good luck with that

          • 3 weeks ago
            Anonymous

            [...]

            Async coroutines made fibers obsolete, but the ((software industry)) sat on the concept for 30 years and didn't tell anyone it existed.

            Nobody asked for Rust and nobody is getting out of bed for it, so there must be some nefarious reason it's getting pushed on us.

            Why do cniles lie though their teeth about Rust and it's achievements?
            Their very post was made possible by Rust at cloudflare?

          • 3 weeks ago
            Anonymous

            >Their very post was made possible by Rust at cloudflare?
            GlowFlare was used by skids who couldn't afford TLS certs before letsencrypt; and is nothing more than an NGINX reseller in the DDoS ~~*mitigation*~~ racket. This isn't a gotcha. I mean, congrats, you have an example of a TLS MITM program in rust, i guess?

          • 3 weeks ago
            Anonymous

            Yeah, posting about Rust's supposed nonexistence all the while being forced to use Rust backed Cloudflare must be a humiliation ritual for you.

          • 3 weeks ago
            Anonymous

            >NGINX reseller
            They dropped NGINX for Pingora because the former was not fast enough.
            https://blog.cloudflare.com/how-we-built-pingora-the-proxy-that-connects-cloudflare-to-the-internet

        • 3 weeks ago
          Anonymous

          >and trips balls the moment you're working with c++.
          almost like everything else?
          are you a nocoder or something? do you even know how C++ works?

  15. 3 weeks ago
    Anonymous

    Twice as productive means they're busy recreating the shit code Google already created but shittier.

  16. 3 weeks ago
    Anonymous

    Double of nothing is still nothing, gay.

    • 3 weeks ago
      Anonymous

      seethe more javajeet.

      • 3 weeks ago
        Anonymous

        >implying.
        I don't know how to code.

        • 3 weeks ago
          Anonymous

          then why did you opine you worthless Black person?

          • 3 weeks ago
            Anonymous

            suck my dick gay. ill frick you in the ass you understand me mother fricker? GET THE FRICK OFF MY TECHNOLOGY BOARD BEFORE I FIND YOU AND TENDERIZE YOUR COLON INTO A BLOODY MESS b***h ILL DESTROY YOU SO FRICKING BAD JUST SEEING A CHAIR WILL FILL YOU WITH PAIN

          • 3 weeks ago
            Anonymous

            Same as the other poster, but no homo.

      • 3 weeks ago
        Anonymous

        Neck it, jeetroony

  17. 3 weeks ago
    Anonymous

    >rewrite
    >productive
    I really don't understand why the trannies think that rewriting something is productive...

  18. 3 weeks ago
    Anonymous

    VAPE NATIOOOON
    WOOOOOO

  19. 3 weeks ago
    Anonymous

    How can they be as productive in Rust as Go?
    Rust is so verbose, obtuse, a slog, and painful to refactor/iterate over.

    What's slowing down the Go devs that they're as slow as the rust trannies?

    • 3 weeks ago
      Anonymous

      > What's slowing down the Go devs that they're as slow as the rust trannies?
      They're too busy tying in "if err != nil { return err }" every other line.

      • 3 weeks ago
        Anonymous

        nta. do you have anything better than strawmans? im sorry you cant hecking c00d your 31337 fizzbuzz in 5 lines instead of 15. it turns out some applications genuinely need verbose error handling to the point where not having secret throws, .unwrap(), panic!("out of memory"), and other error paths is a selling point, and that leads me onto, your point? what is it?

        • 3 weeks ago
          Anonymous

          >nta. do you have anything better than strawmans?
          that isn't a strawman though. it's just a straight fact.
          you'd probably do something like errors.Join(err, yourExtraErr) but it's the same shit noise.

    • 3 weeks ago
      Anonymous

      Rust frontloads a lot of time you'd otherwise spend debugging. You get this with new code too but particularly with refactoring my experience is that once your code compiles again you're basically done
      I haven't timed myself or anything but I can believe it evens out

      nta. do you have anything better than strawmans? im sorry you cant hecking c00d your 31337 fizzbuzz in 5 lines instead of 15. it turns out some applications genuinely need verbose error handling to the point where not having secret throws, .unwrap(), panic!("out of memory"), and other error paths is a selling point, and that leads me onto, your point? what is it?

      >it turns out some applications genuinely need verbose error handling to the point where not having secret throws, .unwrap(), panic!("out of memory"),
      Why are you listing implicit errors together with explicit error handling? You can do panic(err) in Go as well, IDGI
      Rust does make the common case of bubbling up errors far more compact than Go while still keeping it explicit. You just put foo()?, or with anyhow you can put foo().context("some message")? to tack on some more info. You shouldn't take anyone seriously who tells you that this is the productivity difference between Go and Rust but it's honestly very nice

      • 3 weeks ago
        Anonymous

        >Why are you listing implicit errors together with explicit error handling? You can do panic(err) in Go as well, IDGI
        I'm not. Im responding to this sperge:

        > What's slowing down the Go devs that they're as slow as the rust trannies?
        They're too busy tying in "if err != nil { return err }" every other line.

        >

        How can they be as productive in Rust as Go?


        Rust is so verbose, obtuse, a slog, and painful to refactor/iterate over.

        What's slowing down the Go devs that they're as slow as the rust trannies?
        >> What's slowing down the Go devs that they're as slow as the rust trannies?
        >They're too busy tying in "if err != nil { return err }" every other line.

        >Rust does make the common case of bubbling up errors far more compact than Go
        yea i dont care about how your troony lang handles errors. the point is there's a good chunk of the systems and embedded market that cannot accept hidden error paths, especially when they blow up your local context or the entire program, and to act smug about not being aware of these failure modes/error modes is pretty moronic (per 99716793).

        • 3 weeks ago
          Anonymous

          What I'm saying is that Rust's error paths are explicit while still being less verbose than Go's. It even makes it much harder to ignore errors than Go
          You're barking up the wrong tree

        • 3 weeks ago
          Anonymous

          >hidden error paths
          what are you talking about troony? Rust is probably the only language that has the inverse of a hidden error path since all conditions must be handled and you can even annotate returns as #[must_use].

  20. 3 weeks ago
    Anonymous

    Rust is the new Java

    • 3 weeks ago
      Anonymous

      except Java is worse than Rust, so is that a bad thing?

    • 3 weeks ago
      Anonymous

      That would be Go.

  21. 3 weeks ago
    Anonymous

    I literally use Rust for "scripting" tasks now. I just replaced python with it because it's way clearler and way faster to write in general.

    • 3 weeks ago
      Anonymous

      >one off thing I just want to run?
      >lets use the slowest compiling language in the world

      go toddlers afraid of a proper type system it seems.

      no, I just know where the trade-offs are
      Go also isn't as productive as Python is, but both have their uses

      • 3 weeks ago
        Anonymous

        >slowest compiling language
        If you cannot afford good hardware and live in a poor country i can understand why you get triggered by this.

        • 3 weeks ago
          Anonymous

          Did you know that a multiplier is just that, a multiplier?
          No matter what hardware you plug-in, it's slow as shit compared to other languages and this is relevant as long as the slowest one (Rust is the slow one) takes longer than the time you need to lose focus while CI is running, approx. 5 minutes

          Go write that in your diary before you forget it, imbecile!

          • 3 weeks ago
            Anonymous

            What moronic garbage is this sissy on about? I am using cargo scripts feature and it's fast enough. Stop being a poor homosexual b***h.

      • 3 weeks ago
        Anonymous

        >>lets use the slowest compiling language in the world
        >Quick scripts
        Can you read? How many lines of code do you think we're talking about here?

        • 3 weeks ago
          Anonymous

          That is quite literally the point

          • 3 weeks ago
            Anonymous

            ???
            Do you have any idea how much time I've saved so far by using rust instead of python for parsing 100+mb files? It's about 50 times as fast.

            Of course you have no idea, what am I saying.

          • 3 weeks ago
            Anonymous

            I parse log files with pandas. It's very fast.
            Also, stringzilla exists.

          • 3 weeks ago
            Anonymous

            You are such a fricking moron, holy shit.

            Actually have a nice day.

          • 3 weeks ago
            Anonymous

            >filtered by python
            Are you the kind of tard who manually writes parsers in Python with a bunch of for loops and is surprised when it's slow?
            I tried the whole "notebooks in Rust" thing. It's so incredibly unresponsive. Any advantage of runtime is negated by cells that take seconds to just compile.

          • 3 weeks ago
            Anonymous

            I guess he is and he was filtered by your elegant solution that uses C libraries.
            Yea Python can be slower than computers decades ago for basic tasks when you use for loops.

          • 3 weeks ago
            Anonymous

            >uses C libraries
            Akshually pandas is based on Arrow, thus C++

          • 3 weeks ago
            Anonymous

            same principle but good to know, thank you

          • 3 weeks ago
            Anonymous

            Do people actually do heavy duty string parsing in languages other than perl or awk? Every regex type thing I've seen in python is godawful, can't even imagine doing in a compiled language. Usually I just launch awk as a subprocess, move things to csv and then load into pandas or numpy

          • 3 weeks ago
            Anonymous

            yes, i do mine in rust. perl and awk are slow as shit

          • 3 weeks ago
            Anonymous

            Most tasks people use regex for you can just use substring/index operations. If not, use a state machine and pick up a book on parsing I guess, it's not hard once you've written a couple parsers.

      • 3 weeks ago
        Anonymous

        If you were to mimic Rust (and you would still fall short and not be able to control other contributors) with modern C++ features the compile time would be even longer.
        At least Rust optimizes compilation speed consciously for when the compiler works with all those abstractions and that's still on the books.

    • 3 weeks ago
      Anonymous

      I unironically started doing this awhile ago too.

  22. 3 weeks ago
    Anonymous

    >as productive as Go
    lmao no

    • 3 weeks ago
      Anonymous

      go toddlers afraid of a proper type system it seems.

  23. 3 weeks ago
    Anonymous

    Why can't Rustroons just learn to memory managment?

    • 3 weeks ago
      Anonymous

      Why can't Cniles?

    • 3 weeks ago
      Anonymous

      it has nothing to do with memory management, and everything to do with undefined behavior. The fact that C++ can't even have an Option type without UB is criminal

      • 3 weeks ago
        Anonymous

        >muh undefined behaviour
        https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html

        • 3 weeks ago
          Anonymous

          >not exhaustive
          >checks during runtime, while rust is UB free during compile time

          • 3 weeks ago
            Anonymous

            >ub free during compile time
            >compiler relies on llvm which is written in c++ and thus contains the ub boogie man the rustard is so scared of
            your language is not safe

          • 3 weeks ago
            Anonymous

            The fact it's written in C++ isn't very important for this, logic bugs can and do cause miscompilations just the same. That's how a compiler works
            Point is though that Rust is way safer than C++ because most UB comes from programmer error rather than miscompilations, and Rust catches most of these programmer errors
            Yeah it's not 100%, no shit

          • 3 weeks ago
            Anonymous

            >moves goalposts again
            you're more insufferable than ada enjoyers

          • 3 weeks ago
            Anonymous

            "Actually the compiler can have bugs" just isn't a knockdown argument whichever way you turn it

          • 3 weeks ago
            Anonymous

            And you're a dumb homosexual who thinks it's some own that Rust probably shows how broken LLVM is every so often and fixes it for you.

          • 3 weeks ago
            Anonymous

            >rustcel has finally revealed he's a bigot
            if you love it so much get off your ass and start rewriting llvm in rust... oh wait you won't 🙂

          • 3 weeks ago
            Anonymous

            >hates Ada
            yea, it's confirmed you guys are chronic shitposting and genuinely autistic
            no point to engage you, should just be let to rot and wither away

          • 3 weeks ago
            Anonymous

            sorry sweaty lisp is superior

          • 3 weeks ago
            Anonymous

            Well it's not an either/OR. It's about not being an insect while programming. Which you already are in thinking, you're probably just shitposting chronically.

          • 3 weeks ago
            Anonymous

            why would you ever come to this website to have nuanced discussion when the goal is to bait morons into fighting amongst themselves

  24. 3 weeks ago
    Anonymous

    Could be other reasons
    maybe because the c++ teams are maintaining legacy code bases, while the rust/go teams are more likely to be building new ones.
    Could also be that the people using rust/go are younger and have less job security so they work harder to compensate

  25. 3 weeks ago
    Anonymous

    More productive than C++, okay, could be believable. More productive than Go? That's 100% bullshit.

    • 3 weeks ago
      Anonymous

      As productive, not more. Rust has a lot of convenience features that Go doesn't. The iterator methods alone make it believable.

  26. 3 weeks ago
    Anonymous

    congrats, sisters

  27. 3 weeks ago
    Anonymous

    >you end up writing more code when rewriting something instead of maintaining it
    WOAH NO WAY

  28. 3 weeks ago
    Anonymous

    should i just say it?

    topkek this is a skill issue, yes tbf C++ is not as good and simple as C is but still it's much simpler than Rust. Rustschwesters, how do you cope with that awful syntax? I find it unbearable.

    • 3 weeks ago
      Anonymous

      >topkek this is a skill issue, yes tbf C++ is not as good and simple as C is but still it's much simpler than Rust.
      I don't buy this after listening to C++ programmers talk about constructors and initialization and inheritance and implicit conversion. Rust cleaned up a lot with the benefit of hindsight.
      >Rustschwesters, how do you cope with that awful syntax? I find it unbearable.
      How much time have you spent using it? Which bits do you find worse than C++?

    • 3 weeks ago
      Anonymous

      >tbf C++ is not as good and simple as C is but still it's much simpler than Rust.
      lol
      C++ is the hardest language, bar none.
      t. actually uses C++

  29. 3 weeks ago
    Anonymous

    I think the hate for Rust and functional languages in general and even for python to some extent is solely due to autism. it's irrational, it's cult behavior and they are projecting.

  30. 3 weeks ago
    Anonymous

    I like rust, but there is 0% chance that it's as fast to write as a project in go. I can admit that it likely saves time compared to C++ due to better error handling, better memory management by default and better tools to test your code. But go? That is pure cope at this point.

  31. 3 weeks ago
    Anonymous

    >twice as productive
    zero achievements have been made in rust

  32. 3 weeks ago
    Anonymous

    >talking shit about C personally affects me
    Definitely not a cult

  33. 3 weeks ago
    Anonymous

    >my cult is twice as productive as your cult

  34. 3 weeks ago
    Anonymous

    I mean I kind of believe in that being a possibility, but coming from No-Product Google that is worth shit.

  35. 3 weeks ago
    Anonymous

    I've learned as I get older that European opinions are often wrong, less than worthless.

    • 3 weeks ago
      Anonymous

      american from an american company giving a talk in not-europe

  36. 3 weeks ago
    Anonymous

    I just tried to use C++'s std::variant and Jesus christ, Rust needs to kill sepples NOW

    • 3 weeks ago
      Anonymous

      C++ is taking lessons from Java design pattern books, because they're intellectually bankrupt.

    • 3 weeks ago
      Anonymous

      already has in anyone sensible's mind

    • 3 weeks ago
      Anonymous

      You know the best part? Although std::expected is a kind of variant, it doesn't have std::variant semantics, so you can't even use std::visit on it to get a half-usable pattern matching. You have to write if statements and unpack it with .value() and .error() like a fricking caveman.

  37. 3 weeks ago
    Anonymous

    >Rust teams productive as Go teams
    I'm using Go for a backend, if I can get the same productivity with Rust then I got definitely scammed

    • 3 weeks ago
      Anonymous

      I can't believe so many people fell for the gopher, it was immediately obvious how unproductive it is even if you're working with a team of morons. Finally we seem to be out of the era of "google is using it so it must be good" cargo cult

      • 3 weeks ago
        Anonymous

        I can puke out go code in the speed of light, its one of the most productive langs tbph

        • 3 weeks ago
          Anonymous

          maintaining and debugging it is the millstone

  38. 3 weeks ago
    Anonymous

    [CITATION NEEDED]

Your email address will not be published. Required fields are marked *