News for hackers. Stuff that matters.
Re:Pre-auth RCE in Nginx HTTP/2 handling by acdha on Wednesday November 18, 2026 @12:27PM (#50549200)
The bigger problem is lack of liability: we knew C sucked in the 90s, too, but we had three decades of over-confident dudes saying that was user error and _they_ were smart enough to use C correctly.

Then Rust came along and those dudes either tried to say it was too hard (odd contrast, that) or it’d be too much work to rewrite things.

I’m hoping that LLMs will lower the cost of porting for enough people but what would really help is shedding the idea that the status quo is sustainable. Having consequences for sticking with C would help but we need a way to get companies to pay to migrate without destroying open source.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dnautics on Wednesday November 18, 2026 @12:31PM (#50549270)
It's also valid to say that Rust's memory safety is good but the rest of the language sucks. Just as annoying as the over confident c-heads is the rust community that made even countenancing working on an alternative memory safe system a moral sin, which stifled innovation in memory safety. Hell, people barely know that Ada/spark is memory safe (or that sel4 is memory safe C)
Re:Pre-auth RCE in Nginx HTTP/2 handling by antonvs on Wednesday November 18, 2026 @02:40PM (#50551069)
Aside from the overhead of borrow checking, what about the rest of the language sucks, in your view?

To me, its type system and traits design make it one of the nicest mainstream languages. I'd rather be using a functional language, like Haskell or an ML, and I do sometimes, but I don't pick my work based on that. I work regularly with Java, Go, Typescript, and Python, and out of those I find Rust significantly superior on several dimensions.

Python is terrible, Go is basically weakly-typed Python, Typescript barely deserves comment other than that it's impressive that such a fancy type system was bolted onto Javascript, and Java is basically COBOL at this point - reliable, but clunky and showing its age. Attempts like Kotlin to leverage the JVM aren't very convincing.

Gleam looks interesting but I haven't had a chance to work with it yet, and it's hardly mainstream.

You mentioned Ada/SPARK, but SPARK is not really for general purpose programming, and Ada in general has a similar issue to Java, but worse because of its age. It's as if someone really liked PL/I but decided it needed more features and a syntax closer to COBOL.

Re:Pre-auth RCE in Nginx HTTP/2 handling by sophacles on Wednesday November 18, 2026 @03:43PM (#50551872)
What overhead from borrow checking?
Re:Pre-auth RCE in Nginx HTTP/2 handling by FridgeSeal on Wednesday November 18, 2026 @08:44PM (#50555041)
I imagine they are referring to the cognitive overhead of learning to work with it.

Whether that is “something natural to you”, “something you learn and adapt to” or “something you fight with forever” seems to vary per-person, with I suspect, most people falling into the forest 2 categories.

Re:Pre-auth RCE in Nginx HTTP/2 handling by dboreham on Wednesday November 18, 2026 @07:22PM (#50554302)
> what about the rest of the language sucks, in your view

I will chime in here to say that the adoption of async was imho a terrible decision and led me to abandon Rust for most purposes. I want proper threads and CSP-based abstraction.

Re:Pre-auth RCE in Nginx HTTP/2 handling by UltraSane on Wednesday November 18, 2026 @07:36PM (#50554444)
Ownership model is perfect for multithreading but then Rust goes all in on async like WTF?
Re:Pre-auth RCE in Nginx HTTP/2 handling by cozzyd on Wednesday November 18, 2026 @08:55PM (#50555117)
lack of a stable ABI is a big one
Re:Pre-auth RCE in Nginx HTTP/2 handling by dboreham on Wednesday November 18, 2026 @07:21PM (#50554286)
This really isn't true. It's true that those people saying those things existed, but much more recently. Back when all the C/C++ legacy code we depend on today was being written it was the performance penalty imposed by safety that forced developers down that path, not some lack of interest in other options. We were also transitioning from a world where a fair bit of systems code was written in even lower level languages than C (assembler, BLISS, BCPL). The world we're in today effectively began around 1975 when people figured out how to make a C compiler run on an 11/45. All the decisions were pretty much locked in from there on.