After the (temporary) defederation announcement of earlier i checked the Lemmy repo to see if there was already a ticket on the federation limiting option like Mastodon’s that people mentioned Lemmy doesn’t yet have. Not only i didn’t find it, i also saw that there’s about 200+ open tickets of variable importance. Also saw that it’s maintained mostly by the two main devs, the difference in commits between them and even the next contributors is vast. This is normal and in other circumstances it’d grow organically, but considering the huge influx of users lately, which will likely take months to slow down, they just don’t have the same time to invest on this, and many things risk being neglected. I’m a sysadmin, haven’t coded anything big in at least a decade and a half beyond small helper scripts in Bash or Python, and haven’t ever touched Rust, so can’t help there, but maybe some of you Rust aficionados can give some time to help essentially all of Lemmy. The same can be said of Kbin of course, although that’s PHP, and there is exacerbated by it being just the single dev.
I wouldn’t say rust is harder, just different. There aren’t really many languages that are safe in the way rust is safe… Ive done a bunch of intermediate rust tutorials and i actually got the hang of it pretty quickly
I love Go. Sure, it has downsides like it’s error handling is annoyingly verbose, terrible support for functional programming, the standard library is very tiny, and it doesn’t have much syntax sugar. But damn if it isn’t the most easy language I’ve ever used. I think it has the fewest gotchas, the code is generally the easiest to read, and it performs well (especially with goroutines). Code is read far more often than it’s written and ease of understanding unfamiliar code is very helpful for getting people to contribute to your project.
Have you looked at the size of your executables and the runtime with go?
Maybe if you’ve making a web browser or some server process is useful but not for most tools because of the gigantic baggage it pulls along.
a lot of rust’s safety is basically the compiler enforcing things that are already considered modern c++ best practices