Probably someone noticed that it is inconvenient, and on 64-bit machine ints are still 32-bit and not 64.

The computers with 16-bit ints or 9-bit bytes are long gone, but the language still has to carry that legacy.

Also, cells can have scales? Amazing.

Also I wonder how Vadim Gerasimov managed to obtain an IBM PC-compatible computer: where he got the money and what store would be selling that. This shows how unequal and unfair the society became when reforms began at the late USSR. In earlier USSR, everybody would equally and fairly have no computer.

- you need to specify the rules before starting an application. How one is supposed to guess what application will do? Figuring out the correct rules may take lot of time and is impossible for non-programmers. Imagine I want to install 10 apps per day and they should work perfectly, how much time will I be spending writing rules?

- the rules cannot be changed in runtime, for example, giving access to a camera for 1 minute

- the rules are too limited. You can restrict access to a file, but can you restrict access to a DBUS bus? Can you restrict access to audio, video, GPU etc? To /proc filesystem? To a DNS domain? The rules feel like they were written for computers with teletypes from 70s and not for modern machines.

- they do not allow providing fake data, for example, a fake list of WiFi points so that the app thinks it has the access to your geolocation while in reality is doesn't.

So it is some outdated technology unfit for modern day.

What does a user want? The user wants to be able to run anything without any risk and without writing any config files. Obviously it takes a skill to write such OS, and there is definitely a lack of people with this skill among Linux distribution creators.

A system where installation is done using "curl + sudo bash" is the opposite of a safe OS.

What stops you from using a notepad? I do not want my face uploaded to Facebook.

If you have any respect, don't film other people or at least blur them.

Only in Linux - Windows has no problem with swap in a file. Swap partition is an awful idea because you cannot easily resize it.

Zram is also a bad idea, when it is filled, the system starts swapping to a disk, and old pages nobody needs are kept in RAM forever. Zswap is better in this aspect - old pages are pushed to the disk and newer ones kept in memory. But Linux distributions use zram by default.

Also, it seems that many distributions now place /tmp in RAM (tmpfs). Whoever made such decision is not very bright. When you place a large file in /tmp (for example, viewing a large compressed archive which is automatically unpacked into a temporary location), it fills the memory and the systems locks up completely, including mouse and GUI - because bright people developing Linux cannot think of reserving resources for desktop environment to prevent exactly this situation. Why reserve memory for GUI? Obviously files placed into /tmp are more important. Who needs GUI nowadays when you can easily connect over SSH from another machine and kill the misbehaving program.

If you are making a Linux distribution, do not place /tmp into memory. Or at least check how much RAM user has, and add a limit on tmpfs after which files are pushed onto the disk. Also, do reserve memory for window manager with high priority.

Of course, for collecting better telemetry using local AI for analyzing video from camera and audio from a microphone.

Also, I would like no DRM, no serial id, no support for device verification, no trusted environments, re-programmable IMEI, no locked bootloaders, no proprietary code and no telemetry in any form or shape.