• 3 Posts
  • 1.05K Comments
Joined 1 year ago
cake
Cake day: August 21st, 2024

help-circle


  • 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.









  • applications should all look the same. no custom theming.

    there should not be a way to skirt the window manager theming system. i decide what my windows look like and that should be what all windows look like. that way it’s all uniform and easily parseable at a glance, not to mention a lot easier for accessibility tools to hook into. and for that matter, stop inventing new ways to present your application without doing a user study. we have years of user studies available showing what ui elements work well and what shapes they should be to be easily understood. just throwing something together because it looks cool and then shipping it like that should be a punishable offence.