News for hackers. Stuff that matters.
Re:Rust, Zig, and the Futility of “Replacing” C by pjmlp on Sunday February 28, 2021 @12:54PM (#26295296)
Read the comment I was replying to, before jumping into Rust advocacy mode.

> My understanding is that Rust's chief innovation is the borrow checker.

Carp was a mistake, I wanted to refer to Linear Lisp.

Also in the context of worse is better, C and C++ solutions just need to be good enough.

Learn this and advocate properly.

Re:Rust, Zig, and the Futility of “Replacing” C by Rusky on Sunday February 28, 2021 @01:02PM (#26295380)
What makes you think I'm "advocating" anything? My goal is for people to understand the state of things.

C and C++ have had static analyzers to catch "some version" of these problems for a long time now, so presumably anyone asking about borrow checker functionality would be interested in whether that functionality matches Rust's (i.e. is sound).

Re:Rust, Zig, and the Futility of “Replacing” C by pjmlp on Sunday February 28, 2021 @01:09PM (#26295471)
It reads like it.

We should not forget that even if those static analysers aren't sound, they allow to keep using 50 years of eco-system.

Which is why companies like Microsoft, despite all security talk, in the end add support for recent ISO C versions, and have "secure" platforms like Azure Sphere with a C only SDK.

Re:Rust, Zig, and the Futility of “Replacing” C by Rusky on Sunday February 28, 2021 @01:15PM (#26295557)
I don't disagree:

> ("Just" in quotes because of course more of this is great- my point is merely that it's not the same functionality coming to C++.)

Re:Rust, Zig, and the Futility of “Replacing” C by pjmlp on Sunday February 28, 2021 @02:35PM (#26296319)
We agree then, it is better than not trying to improve anything I guess.