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.
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.