• 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle



  • Cargo is really simple, which is great, but also limiting. Maven is much more complex, but for good reason - there’s use cases, especially around multi-artifact projects and version sharing, where cargo would require either some glue or you run into some interesting edge cases. Usually, Rust isn’t used for the kinds of big, wacky projects with a million dependencies that companies write in Java/Kotlin, so those kinds of use cases are considered more unusual.

    Gradle, in my opinion, makes itself complex because it’s all code, is very brittle, and several of its features just don’t work right and require workarounds. When it works, it builds fast and it works well, but getting it to work, and how often you have to get it to work again…not worth it.





  • Majority by number of distros, or only including desktop Linux distros? Because yeah, if you’re including server distros, that’s true, and if you count it by the number of distros, that’s true, but most people use one of a handful of distros on their desktop. Both gnome and KDE have software centers which you can use to install stuff without the command line.













  • So, I think it depends on what you want out of the tag system. If you want it to be a global tag that tags a post similar to how they’re used on tumblr or something like that (I.E: Has meaning not specific to the community it is in), that should be separate from per-community tags, like they’re done on reddit.
    I think per-community tags should definitely be added, similar to how reddit does them (for a good example of how they are used, see /r/talesfromtechsupport). Global tags, I’m not as sure, and if they are added, I think they should be separate from the per-community ones.
    My hesitation for the global tags is that it will create meta-communities, similar to what happens on tumblr, which blurs the line between communities, which makes moderation a little weird.