linuxmemes

It’s pretty easy to uninstall and make certain packages taboo

I remember reading that you couldn't turn it off unless you outright disabled recommended packages. Reading again, I see conflicting statements and it seems like a common thing people take issue with. Though even locking seems to me like it should just be something that happens during explicit removal, if that is a fix.

So I still kind of hate stuff like that.

Making a system either unresponsive or worse, broken. I feel it would be a workflow nightmare of a scale that would beggar belief and it would need constant attention from the maintainers…Something we’d probably not see in our lifetimes

My system is currently outdated and mostly usable, but has 4 different application issues (1 crash, 1 flicker, 1 compiling/library error, 1 feature error)... before I stopped updating, rolling updates gave me a few bad rolls that did not fix some of these issues (and if I'd have rolled not even week later w/o reading the news, I would've been toasted into terminal-fix-it-now-land).

So I'd say there's a lot of room for improvement here. I dream of something that works like this:

• bin.fast: Major.minor.greatest, 7..30 days
• bin.stable: Major.minor.greatest, 30..180 days
• userspace: any version (including non-system package formats), total install/non-shared-dependencies size may influence update frequency (or budget)
  • small things may update always, big programs may even get to the point where it switches the install over to a bin version for you rather than compiling again
• userspace packages may also slow down dependencies

Non-critical applications may be updated less. Security updates or marked-as-needed-fix more. Alternatively, supporting explicit branches (like Godot's 3.X and 4.X) in official repos helps. Maintenance updates (nothing known broken) may be delayed if something seems/is-known wrong (build-bots, user reports or comments, upstream fix needed or dependency too new, admin/maintainer intervention etc)

Ultimately, this could mean an update about every week or slower than once a month depending on packages and if the user encounters issues or not. And I'm sure this may be possible with some package system, but again not something default (and less effective if a package system doesn't provide the needed structure/information).

Hardware wise, yeah I'm otherwise still pretty happy with the performance level I have (and it's a fine target for my own stylized projects, still working on that). A smaller(+more efficient) system would be nice, but GPUs seem to still be behind/lower-value than CPUs though. Polaris would be fine just to make things easier though, not that I want to buy a sidestep especially when the market is so stagnant. Same thing with workarounds that won't be really cheaper either (esp, w/RAM etc pricing).

This is why I am very careful to use a small amount of them as there are a few apps

What I'm talking about was an issue with 1 package due to sandboxing, and it was Krita IIRC (something I don't care about sandboxing on). I think KDE stuff was being pulled in too (I don't use it, but I do use Kate and few other things that use Qt).