#Rust seems to have grown an individualist community, with all its tiny packages hosted in a non-curated repo, with its rejection of copyleft, and with its disregard of #FreeSoftware “community standards” developed by distro folks over the years.
I feel that introducing Rust right into once collectively-developed code bases at the core of GNU/Linux will have unpredictable and detrimental effects.
@civodul This is an interesting take. I am curious to hear your perspective more. My perspective watching the Rust community and now starting to get involved myself is the opposite. The non-curated code repository makes it way easier to collaborate on shared code across projects. Also, it helps a lot that the standard library is decent, unlike C++'s awful standard library.
@civodul Ardour, Mixxx, and Tenacity, which are all written in C++ and share lots of dependencies. But they all have tons of their own code which hypothetically should be able to be shared between them pretty easily, but isn't. Why? In large part because tasks as simple and commonplace as reading files and spawning a new thread are hard to do in a cross platform way in C++. I wouldn't want to do these simple things without Qt in C++.
@meena @civodul The way asynchronous runtimes are decoupled from the standard asynchronous interfaces is a great example of this. It allows asynchronous code to be shared between a native Rust runtime like async-std or Tokio, and it also can be integrated with an external runtime like the GTK Rust bindings do.