If you just reimplement Electron in a native language then you get... Chrome, which is already written in C++. The majority of RAM usage in Electron applications is from the native parts of Chrome itself and a decent ~40 MiB chunk for the Node.js runtime.

The issue with truly random IDs is that inserts are scattered throughout the B-tree index, which cause page splits, fragmentation, and poor cache locality. Using a timestamp prefix makes new IDs sequential, so inserts tend to land near the end of the index, which avoid all the B-tree trashing and improve write performance.

Isn't that exactly what is different about AI automation? AI is more generalized and cheaper to operate.

Manual labor and trades is likely to be one of the last things to go, so the whole "dropout of school and go into trades" crowd may have been more correct than ever, though their original reasoning was not.

Once anyone can generate any game, movie, or artwork they can imagine with a simple prompt, this shared experience will disappear along with it. The amount of content available will fragment the space so much we'll eventually lose the shared experience and novelty that brings enjoyment and fulfillment from these activities in the first place.

You only really need to sandbox when you provide access to tools that are almost impossible to filter correctly, such as a bash tool or a tool for arbitrary code execution.