434 karma · joined September 20, 2023
Most of my work so far has been on the actual music-making interface, but I'm beginning work on the backend now. I've only worked with Django before (for a school project at Georgia Tech), so I'll be deep in the `sqlx` documentation for a while.
There's no manual, so use at your own risk (it's similar to tracker programs like FastTracker and OpenMPT): https://mondobe.com/tracker
This is my first time doing anything with frontend more complex than an image carousel, and I have occasionally felt that I'm in over my head with things like multithreading and audio playback, but it's immensely satisfying seeing the app come together.
I am extremely impressed by the Leptos framework [2], and I'm thrilled that I haven't had to write a single line of JS, even when doing DOM interactions or communicating with web workers.
Once I polish up the tracker frontend, I'd like to add a backend and potentially try to release it as a paid app.
interface Animal {
Circle[13] circles();
// Leftover from Intro to CS, remember to remove
void make_sound();
}From personal experience, the only thing that changed when replacing the "old" Google Assistant with the Gemini-powered one on my Pixel was that it's no longer able to create reminders.
Even more importantly than this, Rust has a major emphasis on backwards compatibility. The author mentions a "hamster wheel" of endless libraries, but, in Rust, nothing's forcing you to switch to a newer library, even if an old one is no longer maintained.
In general, the complexity of your project is completely up to you, and (at least to me) it seems like a lot of the new features (e.g. generator syntax) are trending towards simplicity rather than complexity.