@zeenix@toot.catTl'dr #rustlang is a great collaboration opportunity for @gnome and @kde.
A long long time ago, #freedesktop initiative was created for precisely this goal. While in many ways it was a success story (especially in terms of establishing standards), it came short in one specific aspect: code collaboration.
Most freedesktop (all?) projects were and are almost exclusively developed and maintained by GNOME folks. That's not very surprising, given that C (being that lowest common denominator) had to be the programming language of choice. Just like most GNOME folks wouldn't want to touch C++, KDE folks don't particularly enjoy coding in C either. I know both have their reasons and the point here is not to play the blame game here.
There is not much point in dwelling in the past here but if we decide to write all future infrastructure/non-UI projects (that would have otherwise been written in C or C++) in Rust, there's a great potential for collaboration, I believe.
Talk is cheap, you could say and I agree. Hence why I've taken some steps in this direction already: https://github.com/dbus2/
@valpackett@blahaj.zone@zeenix@toot.cat woah zbus now lives on github instead of fd.o? tfw resistance is futile?
anyway excited for the rusty broker daemon, will definitely make sure it runs well on FreeBSD :)
@zeenix@valpackett yes, we recently moved. gitlab.fdo is unbearable these days. Try contributing there with a new account and you'll quickly see what I mean.
Thanks for doing that. We already have a CI job for Mac and Windows. Probably should add one guy FreeBSD as well (I think GH offers a runner?)
@valpackett@blahaj.zone@zeenix@toot.cat rightttt the new account thing. I forgot, oops. (Surely that's not a forever situation though?)
No, GH doesn't, some 3rd party services do
@zeenix@valpackett it's been going on for months. It's maintained mostly by a few volunteers. I already had huge issues with windows runner.