Eskil Steenberg – I've had it with the security orthodoxy. – BSC 2025 [video]

5 justin66 3 7/29/2025, 8:44:35 PM youtube.com ↗

Comments (3)

RGBCube · 3h ago
This whole rant is uninformed & it seems like the author is completely ignorant of anything happening outside his well.

But I'll bite the Rust rant anyway.

> Where's your SSL?

Right here: https://www.memorysafety.org/blog/rustls-server-perf/

It's an order of magnitude faster than OpenSSL, and almost double the speed of BoringSSL.

> Where's your operating system?

There are lots of OSes written in Rust, but nobody expects them to replace a well-established piece of software like Linux (and _even Linux_ is integrating Rust, because you can't RIIR the kernel overnight). That's why it's shining in the embedded sector, with stuff such as Tock: https://github.com/tock/tock, or many, many other OSes available today. Oxide Computers uses Rust, Volvo writes a lot of their systems in Rust. I also know a few unnamed MIC companies in Turkey using Rust for their software. Anduril also uses Rust.

Rust also runs the Internet, Cloudflare is primarily Rust and AWS is one of the biggest users of Rust. So many more examples but these are the biggest.

Half my environment is Rust: Helix/Zed my editors, my version control system (jj), my shell (nushell), my Window Manager (niri), the build system I'm working on in Rust to build it all, Firefox which is partially Rust, and I actually enjoy using these greatly, because they're fast, well designed and secure.

Has the author written anything in his life that's not games or toys?

Xeamek · 2h ago
Not to mention him saying no one writes java anymore when it literally powers world's most popular OS (android) and double digit percentage of internet backends
geekedcoder · 4h ago
Points made in the rant part: * Security bugs are not more interesting than other bugs. * Lol, why do people even care about security when they upload everything into the cloud. * Stop crying and start fixing bugs. * Security measures are unreasonable, they prevent development progress and consume too much runtime. * Common negative impression of the C memory model is skewed by surviorship bias. * Many weak links in the chain.