• 1 Post
  • 300 Comments
Joined 1 year ago
cake
Cake day: August 21st, 2024

help-circle















  • reading the manual is sort of compulsory if you want to do stuff like changing DEs, and for most people (read: the 99% that don’t know what “operating system” means) the mere existence of a choice is enough to cause paralysis.

    i really do like the new wave of “opinionated” distros like kalpa, cachy and aeon where the system takes care of most issues rather than the user having to deal with them. shows maturity. but this selector screen sort of runs contrary to that. either be opinionated or be fully free, imo.


  • i think that’s calamares, so any distro that uses it can technically do this. the reason most don’t is that you can just add more DE’s after install. i know endeavourOS and openSUSE do this, and i think fedora has something like this too?

    but the main reason is to keep install size to a minimum. if you want your system to be installable without an internet connection you can’t just ship every DE known to man.



  • i mean python is 99% backwards compatible so as long as you tell your tooling you’re working with 3.10 it will warn you about using stuff that’s too new. that’s why the shipping version is usually enough. in general it’s not recommended to have multiple versions of python3 installed at the same time, but if you are a habitual venv user it’s usually not a problem. however i have also run into the issue of some versions being “too new” for a project, where the thing just would not work with newer versions.

    basically, if your issue is only that you don’t want to “contaminate” an older codebase, that can be solved by configuring your tooling. but if your issue is that the thing just doesn’t work with the “wrong” version, you’re probably best of using a container. a user installation of the version you want will work but having multiple installations is annoying.