@civodul Going along with the standard library, one more aspect of Rust, as well as other modern programming languages, that makes it much easier to collaborate is standardized tooling? CMake? Which CMake generator? Meson? Handwritten Makefile? Autotools? Visual Studio project files? Nah, none of that mess. Everyone uses Cargo.

@civodul Another aspect of Rust that makes it really easy to share code is how easy it is to organize code into independent modules and libraries, even within one project.

@tychosoft @codeberg @civodul So if GitHub shut down, with the original design, the entire Go ecosystem would collapse instantly with no recourse without changing how the core tooling works? 🤣 Incredible.

@fnetX @tychosoft @civodul At least you don't need to commit those 500 MB of Node modules into your Git repository.

@tychosoft @codeberg @civodul Go sounds like an even worse shitshow than the Node ecosystem.

@tychosoft @codeberg @civodul It also means that the entire Go ecosystem is *forced* to use one version control system. So not only is it coupled to GitHub, it's coupled to Git. I think Git is great, but I also think it's a horrible idea to *require* one specific version control system.

@tychosoft @civodul I'm not that familiar with Go so I don't quite understand the implications of what you're saying about using the repository name as part of the import paths.

@tychosoft @civodul lol what a terrible idea to couple the symbol names in the code to where the code is located

@tychosoft @codeberg @civodul So the solution to reproducible builds in Go isn't something like Cargo.lock that specifies precise versions of all dependencies with checksums, but literally copying and pasting the entire dependency graph of everything into every package? LMAO

@tychosoft @civodul and people advise me to use Flutter for the GUI of a Rust application 🙄

@tychosoft @civodul lol that's what happens when using something made by Google for essential infrastructure of your project

@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 So, because Ardour and Tenacity don't use Qt, they can't make use of the code in Mixxx that reads audio files from storage in a realtime safe way. Compared to my current experience starting to work on a new audio application in Rust, people working on different projects with different goals have already written libraries for this nontrivial foundational task, and it already works well.

@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++.

@civodul My answer to the lack of copyleft in the Rust ecosystem is to write copyleft Rust code. 😃

@civodul Also, I am really impressed with the way the Rust language is collaboratively developed at scale and continuously evolving without breaking old code.