lfairy

5 ms·

1.
by lfairy 5y ago
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)
2.
by lfairy 5y ago
> 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, polymorphi
3.
by lfairy 5y ago
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 al
4.
by lfairy 6y ago
So you're saying that Haskell's memory safety is meaningless too, because parts of its stdlib and runtime are written in C?
5.
by lfairy 6y ago
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.
6.
by lfairy 6y ago
I might be biased, as I'm the engineer that you're talking about, but that characterization feels unfair. Context-aware escaping is by no means common in the open source world—just look at Jinja or Handlebars. So unless you'r
7.
by lfairy 6y ago
The API in question is stable now, so that will change very soon: https://github.com/lambda-fairy/maud/milestone/1
8.
by lfairy 6y ago
Author here. Yeah, that FAQ was written a few years ago and my opinions have changed since then. I'd also like to emphasize that no Rust template engine – that I'm aware of – does context-aware escaping. At least Maud has it on
9.
by lfairy 9y ago
For the uninitiated: Google dedicates a whole cluster of machines to finding memory safety bugs in Chrome. Finding segfaults is part of their work flow. https://dev.chromium.org/Home/chromium-security/bugs/usi