Rust Programming

I wrote a web server to store markdown documents with links between them, a sort of 'zettelkasten'. Now I've made it into a tauri app that runs on my phone, web server and all, and can sync with the main server in the cloud. Documents everywhere! Front end is in elm and not rust tho.

I've made a few other projects in rust, did a audio dsp thing that is a delay with web controls, made a blinky sketch for the rp2040.

Rust is cool because you can write pretty high level code in it, with lots of libraries to help out, or you can write bare metal code with no OS for embedded.

Anything and everything, really.

I wrote an idle inhibitor in Rust, a GUI WiFi connection manager for my wife, an API client for WriteFreely, I contributed to a Wayland compositor (niri), wrote a library & CLI tools to talk to Kaleidoscope-powered keyboards. I wrote the frontend of my personal search engine in Rust too.

But I also built a Tauri application where the backend and the frontend were written in Rust too. No HTML or JavaScript in sight, not in the sources at least.

Professionally, the answer's the same: if I am allowed to write it in Rust, I will write it in Rust, whether it is a low-level library that talks with hardware, a GUI application, or some web related thingy, or anything inbetween.

The personal project I'm currently working on the most is Nucom, an implementation of Microsoft's Component Object Model.

The IDL compiler for it, which takes .idl files which define COM interfaces and outputs C/C++ headers/source files and Rust modules, is written in Rust.

Originally, this project was all C++, and everything but the compiler still is (which also likely isn't going to change since it involves building dynamic libraries which Rust does not do well at all), but I really did not want to go without Rust when writing a parser/compiler type thing because the language is so much nicer to work with.

My initial motivation to learn Rust was gamedev. Ultimately, you want high performance for games, which Rust can deliver.

Another area where Rust will be pretty much unavoidable in ten years is embedded computing.
So far, pretty much everything in embedded was implemented in C/C++, because you don't have a filesystem there, so you can't use a runtime, like Python, Java et al need. Rust doesn't require a runtime either and is finally a more modern language, with much better tooling.

Well, and where Rust (or C/C++) not requiring a runtime comes in handy, too, is for writing libraries. You can use it to create libraries, which can be called from virtually any language (via the C ABI).

But yeah, as the others said, essentially anything can be implemented in Rust. Moreso than most other languages.
At $DAYJOB, we've got a distributed system with edge components and a backend, as well as a CLI and a web frontend. All of it is implemented with Rust (and some HTML+CSS). For the web frontend, we're using WebAssembly (via the Leptos framework).
That is genuinely a solid reason for us to implement this in Rust, because we only need to know one language.

Various projects. With C I wrote drivers and networking stacks for embedded systems, with C++ I worked for years on a the networking layers of a now long gone smartphone OS. With Rust I've been doing hobby projects like a library+application (win/linux/macos) for controlling WeMo switches on the LAN. Most recent is a Memory+CPU usage monitoring applet for the nascent COSMIC desktop environment.