4 ms·
> the gatekeeping implied here [...] is really toxic It's Theo de Raadt, toxic rhetoric is sort of his brand. But... he has a real point here. It's not about
by ajross 7y ago
> the gatekeeping implied here [...] is really toxic
It's Theo de Raadt, toxic rhetoric is sort of his brand.
But... he has a real point here. It's not about grep or cat or whatever really, those are just the use cases for which OpenBSD would care.
It's that as Rust is reaching the second decade of its history, and despite some outrageous wins in press, evangelism, and general developer mindshare... Rust just hasn't made much progress in replacing exactly the software that it claims to be intended to replace!
Where are the pervasively used compression libraries in Rust? Video and audio codecs? Network stacks? Database engines? System management utilities? PKI and encryption stacks? All that stuff is still in C. After ten years of Rust success!
It's not like no one is using Rust. It's not like it doesn't have success stories (even in the categories above). But they're comparatively rare, still. There's nothing in Rust that rises to the category of "stuff everyone just uses because it's what everyone uses" (c.f. zlib, libjpeg, readline...) yet.
And if there isn't after the first decade, what needs to change to make it happen in the second. I mean, is it maybe fair to say that the window is closing for rust to take over a significant fraction the systems programming world?
- steveklabnik 7y ago> It's that as Rust is reaching the second decade of its history Sort of. It's only been five years since it was actually stable enough for production use. (with a few exceptions of folks who were really invested)
- comex 7y agoAnd: > Where are the pervasively used compression libraries in Rust? Video and audio codecs? Network stacks? Database engines? System management utilities? PKI and encryption stacks? All that stuff is still in C. How many of those projects in any language are less than five years old? The ubiquitously used stuff is mostly much older. But among the projects which are that young, Rust has substantial representation.
- jerf 7y ago" There's nothing in Rust that rises to the category of "stuff everyone just uses because it's what everyone uses" (c.f. zlib, libjpeg, readline...) yet." IMHO, that's basically not possible, so it isn't a fair ask. If the Rust community produced a drop-in replacement that is every bit as good as readline in literally every way... still nobody would switch, because why would they? What's the benefit? You spend all this effort just to trade evenly across. If the Rust community produces something better, nobody's going to use whatever those extra features are outside of Rust itself. This is the category of software that will be last. The question for Rust, and equally, every other ambitious language, isn't really "What percentage of existing code will be rewritten in this new language?" (And by "rewritten", I don't just mean "reimplemented but only your community uses it, but in the sense you mean... it actually replaces the original.) If your answer is any number significantly over zero, that itself represents entrance into the absolute top tier of languages... this is very rare. The question for Rust et al is "What percentage of future code will be written in your language?" On that front, Rust is still on a pretty decent trajectory.
- ajross 7y ago> IMHO, that's basically not possible, so it isn't a fair ask Is it not? There is software in that category written in the last ten years (not as much as in the preceding decade, obviously). How about Docker? V8/node? Most of the wasm ecosystem dates from that period. Actually there was a huge window with TLS implementations once the community collectively decided to move away from openssl, too. Rust didn't hit any of those sweet spots. And I think we should maybe be spending more time asking why.
- jacquesm 7y agoAt a guess because it is much easier to yell from the sidelines than to be exposed with your stuff out in production across major installations. Maturity of code is measured in blood, bugs and overtime, regardless of what language it is written in.
- jerf 7y ago"How about Docker? V8/node? Most of the wasm ecosystem dates from that period." Not a replacement of any previous tech, not a replacement of previous tech, and not a replacement of previous tech respectively. You were suggesting Rust must replace things like "zlib, libjpeg, readline". These are not the same sort of thing. It is "zlib, libjpeg, readline" I was suggesting is far too high a bar to clear to say a language is succeeding; I mean, what other language has replaced them either? It isn't just Rust failing to displace C from those places, it's all the languages. I don't even know what it would take for a language to actively replace C in those positions. What could a language possibly offer to overcome the cost of throwing all that code away? "Actually there was a huge window with TLS implementations once the community collectively decided to move away from openssl, too." This is closer to valid, but still a huge ask. Rust may not have done it but neither did anybody else; SSL is still C. Now you've shifted the question from "Why doesn't Rust successfully replace existing tech?", which is what I was saying is effectively impossible, to the question "Why doesn't Rust have a killer app?". This is a fine question to ask; I don't attack you for asking it. I'm merely defending my original characterization. Still, I suspect Rust is like Go; while there is definitely a significant set of apps now that are implemented in Go that people use because they are the best-of-breed and not because they are Go, I expect that usage is dwarfed by usage of Go that you never see. I see Rust coming up around me in places where it's just happening organically, unrelated to HN.
- sergeykish 7y agoI agree UNIX base is not its niche. But take a look on Firefox: * Video and audio codecs - MP4 metadata parser, Audio backend * Database engines - key-value storage backed by LMDB * Network stacks - A QUIC implentation, SDP parsing in WebRTC * PKI and encryption stacks - TLS certificate store * And more https://wiki.mozilla.org/Oxidation https://wiki.mozilla.org/Oxidation Just five years since first stable release.
- anewvillager 7y ago> Where are the pervasively used compression libraries in Rust? Video and audio codecs? Network stacks? Database engines? System management utilities? PKI and encryption stacks? All that stuff is still in C. After ten years of Rust success! It's not ten or 20 years, the first release of Rust was in 2015. Pre-1.0 Rust was a wildly different language, with green threads, segmented stacks, regular and wild breakage, not really a C replacement! Please understand this point. But anyway here are some projects: https://github.com/ctz/rustls https://github.com/ctz/rustls a TLS library that uses https://github.com/briansmith/webpki https://github.com/briansmith/webpki a pki library https://github.com/burntsushi/rust-snappy https://github.com/burntsushi/rust-snappy a compression library https://github.com/tikv/tikv https://github.com/tikv/tikv a database engine https://github.com/hyperium/tonic https://github.com/hyperium/tonic a gRPC library https://github.com/tock/tock https://github.com/tock/tock an embedded OS https://lib.rs/command-line-utilities https://lib.rs/command-line-utilities lots of CLI utilities which include system management You ask for "pervasively used" but this is not under control of Rust itself. It's not feasible to replace decades old setups in five years. The most widely deployed Rust stuff is in Firefox and some Gnome libraries AFAIK. > I mean, is it maybe fair to say that the window is closing for rust to take over a significant fraction the systems programming world? I don't see why this should be the case.