It is a species of trolling, designed to attract flaming responses and try to paint Rust proponents as arrogant, insufferable know-it-alls whose opinion can be safely dismissed. There's nothing factually wrong in that statement, it's all in the approach.

Non-trolling assessment would be that Rust's safety guarantees help, and help enormously, with the development of robust code, but are not a panacea. E.g., see the results of fuzzing some Rust programs and libraries: those are all bugs detected at runtime, not by the compiler. Note also that all except two, one segfault and one stack overflow, result in a controlled crash with a backtrace, which makes identifying the bug much easier.

It is also clear to everyone who's not a blind zealot that it's impracticable to re-implement every piece of code in Rust. Which doesn't mean that its use in places where it's felt that its safety could make a difference shouldn't be explored.

Came for the Rust trolls, was not disappointed. It's fascinating to see how they incorporate the latest developments into their narrative, and drop things which started sounding ridiculous even to those who don't follow Rust closely. If you want to know more about "some Rust code [that] apparently made its way into Firefox recently", which is the new styling engine, there's a nice high-to-mid-level presentation from one of the developers.

The original Rust compiler was written in OCaml. There was never an official C or C++ version of the front end. The backend of the self-hosted compiler is LLVM, written in C++.

Rust has been self-hosting since about 2011, which is not "most recently" in my book. There is an independent front end written in C++, which generates LLVM IR and still needs the LLVM backend. It is also incomplete, since it lacks the borrow checker.

Sure, if you want to contort your right hand, assuming touch typing the letters according to the rules of the QWERTY layout. The proper touch typing technique is to use the Shift opposite to the key you want shifted. Doing so with the given example, you'd need to switch the Shifts twelve times. I tried, and it wasn't much fun; I'd rather keep the Caps Lock.

If you forgo the customary technique, then yes, Caps Lock may be superfluous. I prefer not to.

Every time I have to type something like SSL_VERIFY_FAIL_IF_NO_PEER_CERT I remember the Caps-Lockoclasts and chuckle to myself.

The first wave of RISC-V users had no intention to have it as a user-facing component. These days it's common for a SoC or a GPU to have its own orchestration/housekeeping CPU, and manufacturers would prefer to avoid ARM licensing cost for that. Nvidia is probably the highest-profile early user; a talk by one of their engineers goes into quite some detail.

I must have caught the very start of account registration purely by luck; I saw that I could open an account, said "why not", and got myself an initial-band-of-conspirators sort of UID. Once, my day would start with a visit to /., with frequent refreshes. I still lurk regularly, but the stories and comments are kind of... predictable. There's almost a retirement home kind of atmosphere around the place -- but maybe that's my twenty years older self projecting ;)

Not necessarily. Latin homo can, and usually does, stand for "human being" in general. Male and female of the species are vir and mulier, respectively.

That's why nobody seriously uses Goggle. Now if you tried Google, you'd get a snippet mentioning a "self-hosting compiler written in Rust" as the first result.

(Yes, Rust's code generation backend is LLVM, written in C++. Don't try to build strawmen out of this.)

There are still some two-digit UID lurkers. I must admit I haven't seen a single-digit UID for a very long time.

The phone manfacturers do, and for them it's enough that Android is more open than iOS (which it actually IS, for any reasonable definition of open).

So, pray tell, what made those cheap-ass handsets possible?

It's good enough for lurking and offhand reading. Yes, layout glitches and general slowness are annoying, page-width ads for inane apps even more so, but it's the same ugliness on all kinds of mobile browsers I've tried.

Responsive design is not new. Summary: don't make a separate mobile-only site, but style the content so that it adapts itself to various device sizes. Nice if you can pull it off, but requires careful design in order to be both effective and maintainable.

It's an old, but relevant, joke:

The First Law of Economics: For every economist, there exists an equal and opposite economist.

The Second Law of Economics: They're both wrong.

The update is in the CR repo because of the preparations for the release of CentOS 6.7. Short explanation here (with the link to the page explaining how to enable the additional repo), and a couple of longer explanations further down the thread.