@tshepang testing is fine, but nightly features in crates often block the packaging of said crates. As most distros only ship the stable rustc this is an issue for packagers like me.
I wish #rust devs would not use nightly features the second they become available.
Natürlich wieder ein "Klischeebayer" mit Lederhosen und Gamsbarthut. Auch lustig dass unter den vielen Kindern aus allen möglichen Ländern auch ein bayrisches ist.
@bilboed can also really recommend organicmaps, sometimes I feel OSMand to be a bit clunky UI-wise. Regardless, both are great apps.
@mirabilos true. A big part of the issue is some devs hardcoding bit encoding to amd64 (and caring about arm*) at most. I had to patch a lot in rust-land when it came to packaging. imo it's still better than C++. coreutils or gcc for instance will never be replaced because it has matured pretty well and C allows it to be really portable.
@mirabilos It's not all bad imo. I strongly oppose the "rewrite everything in rust" paired with a "oh shiny new stuff" but there are some nice applications written in Rust out there. It's not as architecture-independent as C, granted. The need for C will also never disappear as you can't go more low-level than C (except ASM).
@gamingonlinux systemd suffers from feature creep and alternatives should be explored. Why does my init also need to start ntp or dns resolving? It doesn't, that's why I'm running sysvinit and openrc. Linux should be about choice, except it doesn't feel like a choice when it come to initsystems. Very few distros exist that even provide an alternative.