It's so over c sisters...

It's so over c sisters...

It's All Fucked Shirt $22.14

Yakub: World's Greatest Dad Shirt $21.68

It's All Fucked Shirt $22.14

  1. 2 months ago
    Anonymous

    you lost your opportunity to write "Csters"

    • 2 months ago
      Anonymous

      cisters? our response?

  2. 2 months ago
    Anonymous

    >video codec in the kernel
    that's for Black personcattle

  3. 2 months ago
    Anonymous

    the way they're pushing this is not organic. the glowies have some backdoor in rust so they want it on everything

    • 2 months ago
      Anonymous

      This. Probably in the package manager as it install whoeverknowswhat when you setup your project.

    • 2 months ago
      Anonymous

      What do you mean “pushing” it? People are writing code in Rust because it’s the modern successor to C/++. C is too old, archaic and primitive outside niche embedded platforms and C++ is a complete clusterfrick of kitchen sink features with zero design cohesion.
      Rust is a fresh start with better defaults and younger developers love it.

      • 2 months ago
        Anonymous

        If M$ and feds are pushing it, it's not organic. Don't know if you got the memo but institutional trust is at an all time low.

        • 1 month ago
          Anonymous

          > organic
          Why am I supposed to care about that. All this language shit has never been organic.

    • 2 months ago
      Anonymous

      Most proprietary compilers have code injection/backdoors. Has anyone combed through the Rust compiler for glow? Yeah, didn't think so.

    • 2 months ago
      Anonymous

      Most proprietary compilers have code injection/backdoors. Has anyone combed through the Rust compiler for glow? Yeah, didn't think so.

      Ken Thompson put a backdoor in C. Everything you accuse Rust of doing is something C did.

      • 2 months ago
        Anonymous

        What was it?

      • 2 months ago
        Anonymous

        >Thompson put a backdoor in C.
        It was easy to spot. You wont ever spot them in Rust

        • 2 months ago
          Anonymous

          So easy that nobody fricking noticed
          Good job anon

    • 1 month ago
      Anonymous

      all hardware and software has backdoors
      but yes. the push isn't organic/natural
      but thats because trannies who use it are also not natural

  4. 2 months ago
    Anonymous

    Rust doesn't work without C/C++. It is not a self-hosted language as it depends on a C/C++ backend.

    • 2 months ago
      Anonymous

      IIRC it was written in Haskell and then they translated that to c in order to call it 'self hosting' but the auto-translated code is a mess, also there's no way to back port modern Rust to its Haskell codebase because modern Rust extensions are written in Rust but older ones are in C. They're up to over 4000 RFCs now.

      Basically it's a hot mess.

      • 2 months ago
        Anonymous

        It was actually Scheme and they hand translated it into continuation passing style and then used a macro to turn that into assembler, but they lost the original source because the guy who had it met a leprechaun

      • 2 months ago
        Anonymous

        It was actually Scheme and they hand translated it into continuation passing style and then used a macro to turn that into assembler, but they lost the original source because the guy who had it met a leprechaun

        Wasn't it ocaml?

        • 2 months ago
          Anonymous

          Yeah now that you mention it, I think you're right. One of those weird anorak languages.

          • 2 months ago
            Anonymous

            Boffins, innit?

      • 2 months ago
        Anonymous

        They wrote the bootstrap compiler in OCaml, wrote a self-hosting compiler in Rust, then used the bootstrap compiler to build the self-hosting compiler. Business as usual. No C involved, no auto-translation.
        Years later somebody else made another bootstrap compiler that can compile Rust code to C code, maybe that's what you're thinking of? It's not involved in everyday development.
        >They're up to over 4000 RFCs now.
        And C has over 3000: https://www.open-std.org/jtc1/sc22/wg14/www/wg14_document_log.htm

        • 2 months ago
          Anonymous

          >And C has over 3000
          C's been around for what, 50+ years though?

          • 2 months ago
            Anonymous

            C's documents only started with the standardization process, almost two decades in.
            It's silly to compare them for other reasons, WG14 papers don't have the same role in the process as Rust RFCs. Really the point is that scary number! isn't meaningful

          • 2 months ago
            Anonymous

            >C's documents only started with the standardization process
            That's incorrect.

          • 2 months ago
            Anonymous

            The ones on that list do by the looks of it, if you're talking about other documents then I didn't count those. (Rust of course also had various things going on before its current RFC process.)

          • 2 months ago
            Anonymous

            >The ones on that list
            C's "documents" started with the reference manual included with Unix.

            ANSI C < K&R C.

          • 2 months ago
            Anonymous

            When I said "documents" I meant the formally numbered documents that I'd been talking about in the previous post, sorry if that wasn't clear

        • 1 month ago
          Anonymous

          >No C involved
          There is C++ involved because the Rust compiler spits out completely unoptimized LLVM IR.
          LLVM is the only reason why Rust isn't slow as shit. Basically all the optimizations happen in LLVM.
          It also doesn't natively support any targets, and relies on LLVM (or soon rustc_codegen_gcc) to even run on actual hardware.

          • 1 month ago
            Anonymous

            What does C have to do with LLVM?

  5. 2 months ago
    Anonymous

    >~~*99288977*~~

  6. 2 months ago
    Anonymous

    You practically need a supercomputer to compile Rust. Whichever way you try. There are 4+ year out of date instructions for trying to bring it up in Haskell out there, that seems to actually work, but you're left with a 4 year out of date Rust which isn't compatible with nu-Rust.

    All code will go out of style as time goes on. We've seen Python go through two major revisions even though it worked fine. Consequences are you have to rewrite everything. Perl is now stuck in maintenance mode, it's "done" because nobody adopted the supposed next version. That's actually good - it has everything you need already, and your old code Just Works. Same with C / C++ / Common Lisp / etc. I downloaded all the files from the Unix History site, all the old tapes, with all the code for the whole system, and nearly everything compiled unchanged.

    • 2 months ago
      Anonymous

      Bro why are you compiling the compiler? Don’t you have better things to do?

  7. 2 months ago
    Anonymous

    >kernel build time increases by few hours
    sure love these fricking trannies

    • 2 months ago
      Anonymous

      >few hours to compile Linux
      Have you tried not being poor?

  8. 2 months ago
    Anonymous

    is the gcc rust merged yet

    • 2 months ago
      Anonymous

      No.
      GCC backend for rustc seems to be still going full steam.
      https://github.com/rust-lang/rustc_codegen_gcc

      • 2 months ago
        Anonymous

        I think that he is talking about the gccrs project, not the codegen one.

        https://github.com/Rust-GCC/gccrs

  9. 2 months ago
    Anonymous

    gccrs -fno-borrow-checker glowies_btfo.rs

  10. 2 months ago
    Anonymous

    >VP9
    >Kernel
    Wait what? Why would that ever leave userspace?

    • 2 months ago
      Anonymous

      Speed

      • 2 months ago
        Anonymous

        i hope we someday will have gnome running in kernel

        • 2 months ago
          Anonymous

          GUI in the kernel is how Windows works.

          • 2 months ago
            Anonymous

            no wonder it's so smooth

  11. 2 months ago
    Anonymous

    >think in the poor memory safety

  12. 2 months ago
    Anonymous

    Another proof of concept that hasn't even been mainstreamed.
    Stop gloating, write more Rust code.

  13. 2 months ago
    Anonymous

    >let's make things slower so we can keep writing bad code
    What the frick is going on?
    Why is everything getting fricking worse every single day in every way imaginable?

    • 2 months ago
      Anonymous

      What's slower, buddy? Be specific

  14. 2 months ago
    Anonymous

    skill issue

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