• 0 Posts
  • 25 Comments
Joined 4 years ago
cake
Cake day: April 27th, 2023

help-circle

  • Let me ask a question, then: why were the Linux kernel and the Linux ecosystem written in C rather than Python?

    … because C is a systems langauge that you can use to build a kernel? While Python is an interpreted runtime that cannot target bare-metal?

    Rust can easily take the place of C, as Rust can also target bare-metal. It can do everything that C can do (perhaps aside from compiling to some very esoteric platforms). The reason Linux is written in C is cause C was the best option at the time, not because C is some magical language that can do stuff that no other language can.

    Also, just because Linux was written in C doesn’t mean it is the best-known, most famous or most widely used language. Python is much more well-known and widely used than C.



  • I don’t know where you’ve heard this, but none of it is true. Rust is definitely used for low-latency trading, and that’s actually one place where it really shines.

    sharing memory addresses across code intentionally having the same address written to and read from across threads. Something rust is sort of designed to not support.

    C++ does not “support” that either. C++ will let you write that code, but if you write code like that in C++, it’s undefined behavior and trust me, no low-latency trading firm wants undefined behavior in their trading software (just imagine what could go wrong…).

    Rust helps you avoid such issues. However, Rust definitely “supports” undefined behavior in the exact same way. If you want to share mutable pointers across threads and you don’t give a crap about undefined behavior… I mean, that’s really, really stupid but you can just write unsafe and then you can do exactly what you can do in C++ as well.



  • but no language can take the place of C

    Why do you say that? I definitely think Rust can take the place of C. Not just can actually, I’d go as far as to say that Rust should take the place of C. C is much too unsafe to be used in today’s age. There’s really no excuse to use a memory unsafe language today if you’re starting something new.

    It would not have been better if it was written in C. Rust is just as fast and much better.


  • I’m a professional software engineer writing Rust for many years now.

    Honestly, I am very happy that AI is using Rust. Much better that AI uses Rust than Python! If you think AI written Rust is bad, you have no idea how sloppy AI written Python is.

    Rust is a great language. Turns out the same stuff that makes it great for humans also makes it great for agents. This is not a bad thing, this is a win-win.

    Historically, Rust’s biggest disadvantage has been how hard the language is to write and how much you sometimes need to fight the compiler. This disadvantage is quite effectively mitigated by AI, since you can let the AI fight the compiler and write most of the code. So you get all the advantages that Rust brings with basically none of the downsides.

    I’m just happy that Rust was invented before LLMs. If Rust did not exist before LLMs, the code the AIs would be writing would be a lot worse.

    Hope that answers it.


  • As a counterpoint, sloppy projects are being shared all over and it’s basically spam at this point. Even /r/rust had to disallow code projects, because there was simply way too much slop being posted all the time.

    People share projects because back in the day, a project with hundreds of thousands of lines of code with a cool website and a lot of features were evidence of a lot of hard work, a lot of design decisions and a lot of tradeoffs.

    Vibe coding has made that a bad metric. These things no longer mean that any actual work has been dedicated to this project. Anyone could use an afternoon prompting an agent to build the same thing. There is no value in sharing such a thing. At best, it’s worthless and at worst, it’s borderline a scam, an attempt at disguising a project as something it isn’t.




  • I very much doubt the AI use is confined to the frontend. But I don’t see why the frontend is fine to vibe code while other stuff is not?

    Using AI as a tool is fine. It can be very useful for programming. But “vibe coding” is using it to an extreme degree where the AI is producing almost the whole thing, with a very small amount of guidance or design from the user. That’s what I would object to. Such a thing has very little value, anyone can vibe code such a thing.