Jajcus

We have the same about a shit whip – „z gówna bata nie ukręcisz”

In Poland it is „nosić drewno do lasu” (bring wood to the forest). Similar, but a bit different (pointless not just by being pointless, but by being impossible): „nie zawrócisz kijem Wisły” – ‘you won’t turn Vistula (our biggest river) with a stick’.

Non-toxic glue would be starch or gelatine - both used as base of some ‘real glues’, both with valid culinary use, including exactly this use case. We just don’t call those ‘glue’ in this context.

Also not a fan of #16 since it sounds to me like forced labour for the poor

That is how actually that worked in some (if not all) communist countries. No unemployment, but people (mostly those ‘undesirable’ for various reasons) would be sent to hard work in bad conditions, which would often cost their health or life. The other side of the coin was: everybody had a job and little fear of losing it, so people rarely treated the work seriously enough. There were factories full of workers, but so inefficient, that nothing was produced in sufficient demand. People had money, but little to buy with it.

The idea is you package the software once and it works forever, because all dependencies for it are provided in the exact right version. And the dependencies may include things that would not be included in the base system (like super new versions of some important libraries).

That is true, but that is also the problem: both the package and all its dependencies may be left never updated.

In traditional Linux distribution, like Debian, every package must be compiled within the same system, which usually means specific version of all key libraries. And when the key libraries are upgraded some packages compiled for older versions won’t work, the package might not even compile with newer version of the libraries. And it is often not possible/practical to provide multiple different version of libraries (or other shared system components). The result is distribution developers have a lot of hard work updating all the packages. When there is no one to fix a package for the next version of the package, the package will be removed from the distribution. That happens when package is not maintained upstream and/or no one cares enough to maintain it in the distribution. In that case – is it worth to keep it?

Snap makes packaging applications much easier, and more decoupled from the operating system ‘core’. Less maintenance is needed… but that also means less maintenance will be done, which is not necessarily good.

On the other hand, Snap allows application to be maintained more rapidly than the distro core – in that case it can make things safer – fix in applications and their dependencies can be fixed that it could be done in the normal Debian release process. But that depends on maintainers of the specific snap and its dependencies.

Android is hardly open source these days.

You mean they choose not to support Linux. Still sounds like they are to blame, not Linux.

Then my recent research was wrong - I tried to make it work and failed. Then read somewhere it is not supported. But it can be that it is valid EFI configuration, but not supported by Windows and some firmware implementations.
I don’t think I have ever seen an EFI firmware which was not broken in one way or another.

On EFI systems all bootloaders are supposed to reside on a single partition. EFI does not support multiple ‘EFI system partitions’, so operating systems have to share a single one. And this is usually not a problem if it is the one Windows choose. The problem most often is broken EFI firmware which fails to correctly handle adding and removing boot entries. Or Windows, which fails to boot if anything changes (disk order and such), even though everything is still available.

They destroy everything they touch…

I am only happy for the damaged they made to MySQL popularity. ;-)

Making most of the internet dependent on ad revenue was a bad idea in the first place.

Kopia or Restic. Both do incremental, deduplicated backups and support many storage services.

Kopia provides UI for end user and has integrated scheduling. Restic is a powerfull cli tool thatlyou build your backup system on, but usually one does not need more than a cron job for that. I use a set of custom systems jobs and generators for my restic backups.

Keep in mind, than backups on local, constantly connected storage is hardly a backup. When the machine fails hard, backups are lost ,together with the original backup. So timeshift alone is not really a solution. Also: test your backups.