I have a 10 year old Canon MP280 still going strong. It’s one of the ultra cheap ones, I believe originally sold for something like 20$ at a sale. The only problem it has nowadays is that it occasionally makes some ink blotches in a corner of the page.

They actually call the android releases “cookies” because of this tradition for the code names. You can read phrases like “This will be fixed in the next cookie”

These are Android API levels: https://apilevels.com/

Look up preemptive task scheduling. Basic processes will get interrupted after using a too long time slice.

I had this and really liked it! The physics engine was craaazzyy 😂

Yeah it’s many years that I haven’t had to specify z, j etc.

Hmm you need to download some more RAM

There’s another aspect than size that I feel people overlook: security updates. When e.g. libcurl is duplicated in a million places, how do you update them all when a critical security issue is discovered in it? Who will update all the random flatpaks, snaps and docker images that happen to include it?

If you run testing or unstable there will be updates available very very often. But, you choose when to update, you don’t need to update anytime an update is available.

You should know what you’re doing and expect this if you’re running it. Otherwise, you should use stable. With stable, you’ll typically just have security updates until you choose to update to the next stable, which typically is released every other year.

rsnapshot