Okay, what actually uses Rust
45 points by blyxyas
45 points by blyxyas
Saddened to not see fish, the shell, on this list considering they pulled a RiiR with no fanfare and I haven't noticed at all while using it.
Same. I've used fish for years and didn't notice a single difference. I'm a huge rust fanboy but even that is impressive to me.
especially since nushell in unusable and made it on here. why no love for the shell people actually use?
As a daily user of nushell, what makes it unusable for you? The only thing I really miss is detaching GUI applications I launch...
last time I tried it, it was literally impossible to run go test ./… and such because it tries parsing paths specially and would transform that last arg into ../..
As another daily user of nushell, what isn't usable? I've been using it at work since late-2022 and have had a relatively smooth ride. I've even managed to socialize it to other colleagues who do similar levels of interactive work (we are legion, there are dozens! dozens of us 😆).
I think saying “Coreutils is being rewritten in Rust” makes it sound like this is a GNU project that’s clearly intended to supersede the C Coreutils implementation, which is not the case as far as I know. Perhaps it would be better to say “A rewrite and drop-in replacement of GNU coreutils in Rust is being developed and currently used by Ubuntu” or something along those lines.
Does this mean it's no longer GNU/Linux, but Rust/Linux? (please ignore the existence of glibc/gcc for this joke)
The Rust coreutils project is MIT licensed, so GNU is out in any case.
Stallman's rationale was always disingenuous. He defined the OS as everything you need to self-host development using emacs in a text terminal and not one iota more, so GCC padded out GNU's proportion while X11 was disqualified, despite most people considering a GUI an essential part of a development and/or desktop OS.
Years ago, I read a blog post which laid that out including graphs, but it was before I'd started rigorously bookmarking everything I might want to see again and I've never been able to find it since.
I believe this is missing a couple notable ones.
Signal uses it heavily on client and server
Volvo cars uses it for the ecu
The Amazon Prime Video app on tv
Lets encrypt for certs and ntp
mullvad VPN uses it for the their apps and servers
tailscale has a rust library
reddit uses it as a wasm markdown parser
firefox's css engine is fully rust
chrome uses it for memory safe fonts and some other bits
android has a large rust bridging layer
pixel has a rust based firmware for the baseband
x / twitter uses it internally (no idea for what)
neurolink (has job openings for rust but unsure if they use it)
andruil uses it for drones
Helsing uses it for drones as well
oxide computers uses it for literally everything
Cloudflare also uses Rust broadly throughout the company, not just in Pingora. It's the default language for new projects that aren't built on Workers.
SmartThings was a very early adopter (2018?), and it's now built into many Samsung appliances. You might have Rust inside your dishwasher and not know it.
Volvo just uses it for the ecu, or for other controllers as well? Also, is there a write up for how they use it? This seems really interesting.
For now it's just the ECU AFAIK.
They have an NDC talk about it, available on YouTube: https://youtu.be/vBofCW8j70A
Is this a joke? Rust is super popular and this list has no chance of being even close to comprehensive.
Today I’m presenting a non-exhaustive list
I’m highlighting the most talked about and significant.
If you know of a project that uses Rust that is not mentioned, please get in contact with me!
I've now changed the "The full list" title into "The (not) full list". I just wanted to highlight some places that use Rust and possibly serve as an index for people looking for real progress in the language.
It says the arxiv “uses” typst, is that true? It’s still not yet a supported format: https://info.arxiv.org/help/submit/index.html#formats-for-text-of-submission
I'm a developer at arXiv. arXiv does not use typst and currently does not accept typst papers. There is a positive opinion of typst by people at arXiv but it is not on the roadmap right now.
We do use a Rust program to convert the LaTeX of papers to HTML. This is an area of active development and going well.
This is fixed, I had watched a talk by an arXiv developer and misunderstood that it was already implemented.
No. There was a talk in February at the Typst meetup by an arXiv engineer on what the blockers are for getting Typst in, and those will take some time to resolve: https://youtu.be/zNZlAbCOjd8
There are some production high-bandwidth communications satellite systems in low earth orbit running Rust-based firmware.
Since I don't know if my cross-instance mention on Mastodon worked, I'll say this here too:
- VSCode/VSCodium bundles ripgrep for code search. (https://code.visualstudio.com/updates/v1_11#_text-search-improvements)
- yt-dlp recommends deno for solving challenges (https://github.com/yt-dlp/yt-dlp/issues/15012)
- You mentioned ty and ruff but missed uv.
- The COSMIC DE being used on Pop!_OS as of 24.04 LTS is written in Rust on top of iced. (https://blog.system76.com/post/pop-os-letter-from-our-founder)
- fclones, a duplicate file finder so concerned with speed that it does stuff like physical-layout-aware traversal. (https://github.com/pkolaczk/fclones)
The history of computing teaches us that there is no such thing as a „silver bullet“ programming language, and the idea that everything will one day be written in some „perfect“ language is pure utopia. Despite this, new generations of programmers come along, deeply convinced that their particular programming language is the best.
There not being a perfect language does not mean that there isn't a best language, out of the ones that currently exist, for your circumstances. Nor does it mean that we cannot or should not try to make even better languages and move to them.
So what do you suggest we do instead, that we all continue to write in assembly?
Previously, on Lobsters, I said:
Each language circumscribes a tribe consisting of fluent authors and users and a commonsense viewpoint. Kell and Jakubovic are focused on the problem of fragmentation: the cost of maintaining a machine scales with the number of different viewpoints used to build its associated theories. This doesn't mean that we should invalidate or destroy viewpoints, but that we should seek generalizing principles which allow us to manage a diversity of theories with a modicum of viewpoints.
We should not stop creating new languages. We should be humble about what a new language gives us in expressive ability as well as what it costs us in fragmentation. We should also be aware that fragmentation and defragmentation can be policies, and as such can be politically motivated or partisan positions.