BatmanAoD

I mean, if you're talking about CVEs permitting attackers to get control of the hardware of lots of systems, then yes, I agree

There were memory-safe languages long before C was invented, though; C was widely considered "dangerous" even at the time.

WASM has no native ability to access most web APIs, including the DOM. JavaScript is literally unavoidable on the front end.

Genuine question: if you're writing a new CLI utility, why not Rust? This is arguably where Rust has most excelled, most famously with ripgrep.

Oh, trust me, Qt is still primarily C++. It's effectively a massive set of C++ libraries.

I mean to be fair, that's a pretty useful tool.

Oof, slow compile times to target, of all things, the JVM? Implicit methods? Some(null)? Function call syntax where the difference between a tuple argument and a sequence of non-tuple arguments can be determined by whether or not there's a space before the parentheses?

There are definitely some major issues with Scala.

I was a professional C++ developer for several years, and came to the conclusion that any professional C++ developers who don't acknowledge its flaws have a form of Stockholm Syndrome.

Well, except "robust", unless you have very strict code standards, review processes, and static analysis.

(And arguably it's never elegant, though that's almost purely a matter of taste.)

I've met people with C++ Stockholm Syndrome, and I think their trajectory is different. There's no asymptotic approach toward zero; their appreciation just grows or stays steady, even decades into their career.

The logo and "join our Discord" text are more than half cut off for me. Is that the original cropping, or is it a client (Jerboa) issue?

Rust is extremely geared toward maintainability at the cost of other values such as learnability and iteration speed. Whether it's successful is of course somewhat a matter of opinion (at least until we figure out how to do good quantitative studies on software maintainability), and it is of course possible to write brittle Rust code. But it does make a lot of common errors (including ones Go facilitates) hard or impossible to replicate.

It also strongly pushes toward specific types of abstractions and architectural decisions, which is pretty unique among mainstream languages, and is of course a large part of what critics dislike about it (since that's extremely limiting compared to the freedom most languages give you). But the ability for the compiler to influence the high-level design and code organization is a large part of what makes Rust uniquely maintainability-focused, at least in theory.