Re-creation of someone else's post because the original was removed and I found it funny when I first saw it
this post was submitted on 25 Sep 2023
1150 points (92.3% liked)
linuxmemes
21088 readers
1421 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Unpopular opinion: flatpaks enable lazy developers to keep old versions of required Python dependencies working longer.
And that is bad?
Yes.
Yes. Lack of clarity on what python version to use causes me pain on a regular basis.
If only there was a way to bundle it all together, like in some sort of pack...
I doubt bundling things together in some sort of pack would avoid every problem with python versions I could have. That doesn't prevent a given python version from being marked as "end-of-life" and no longer receiving security patches.
Most software is produced and maintained for use solely by the company that produced it, and probably by people who are not experts in using python, so hiding the complexity that python versions and dependency versions are coupled seems like a bad idea, especially when one wants to limit the number of versions of the same software that is installed (and therefore re-use executable files to save disk and CPU usage and avoid accidentally using the wrong version of a program).
I have not interacted with
flatpakin a professional environment, so I doubt I have been directly harmed by it. However, reducing the importance of quickly upgrading software after new versions are released is probably harmful overall: performing an upgrade will usually make development easier (so making it harder for me to pitch to managers that an upgrade should be done is harmful to my morale), and incentivizing having multiple versions of the same program accessible on the same system makes surprising problems more likely.I think it's fine as long as they aren't terrible insecure. But if they're using an old runtime, people will bother them about it.