HackerTrans
TopNewTrendsCommentsPastAskShowJobs

lfairy

no profile record

comments

lfairy
·5 năm trước·discuss
BTW, this article explains how Rust releases work:

https://doc.rust-lang.org/book/appendix-07-nightly-rust.html

It's a release train, similar to that used by Chromium and Firefox.

Edition releases (e.g. Rust 2021) are reserved for breaking changes only, and to retain Rust's stability promise, are opt-in.
lfairy
·5 năm trước·discuss
> By the way the difference is that Rust is not a standard, thus is easier to evolve (the process is much shorter).

Another thing is ABI.

C and C++ are ABI-stable, which means that many historic mistakes (intmax_t, std::regex, polymorphic allocators) are impossible to fix.

Rust only promises source compatibility, not ABI compatibility, so it has a lot more freedom to tweak its design.

https://thephd.dev/binary-banshees-digital-demons-abi-c-c++-...
lfairy
·5 năm trước·discuss
I think it's less "passion" and "focus", more his position as the Linux lead giving him first-hand experience with change control at scale. He didn't need a product manager to gather requirements, because he already knew them.

That's basically what ItsMonkk is saying, but I think it's worth making it more explicit. Because a one-in-a-million engineer is not replicable, but a deep understanding of your users' needs is.
lfairy
·5 năm trước·discuss
So you're saying that Haskell's memory safety is meaningless too, because parts of its stdlib and runtime are written in C?
lfairy
·5 năm trước·discuss
Yeah, Rust is about the simplest language that guarantees both memory safety + low-level control. Almost all of its complexity comes from having to satisfy both.