3 ms·

Isn't that exactly the point? Multiple groups can develop their "right way" and you can pick and choose which way you prefer. As for being "one update away fro

• AnIdiotOnTheNet 6y ago
  > Isn't that exactly the point? Multiple groups can develop their "right way" and you can pick and choose which way you prefer. In theory. In reality you just end up having to deal with all of them simultaneously to get your workflow going because you're using tools from different authors who all have their opinion of what "the right way" is. > As for being "one update away from breaking" this is an issue on any OS, at least with Linux you have the choice not to update or even roll back. Again, in theory but not in practice. Because of the repo/pacakge manager model that Linux systems insist on using, and because there's no such thing as a separation between 'system' and 'application', failure to update often means you are unable to use up-to-date software entirely. Well, unless you want to set up a build environment and compile your own version of that software, which is utterly ridiculous.
  • bzzzt 6y ago
    > you're using tools from different authors who all have their opinion of what "the right way" is. This is in fact an issue on any platform right now. > there's no such thing as a separation between 'system' and 'application', failure to update often means you are unable to use up-to-date software entirely. Isn't that why Flatpak was invented?