Your second point of trading loot and items got me thinking about my Steam CS:GO skins. Why should I trust a centralized entity like Steam who could at any moment decide to delete all my skins or remove my account for whatever reason with my skins, vs storing those skins in a wallet on a public blockchain for example to keep it’s value and always allow trading? Ofc there will always be a “centralized” smart contract but at least they can’t make changes to it if the smart contract code is audited ,

Will it store my ROMs

I would like to try #2 but for some reason my 5900x doesn’t have graphics so I literally need to buy a whole other GPU for this

Kinda cool but shit $45 for a piece of silicone those margins are insane.

The physical keyboard is just a tool. There are alternatives like speech-to-text software, virtual keyboards with swipe features, or stenotype.

The goal should be to use whatever is most effective and efficient for yourself, so if Gen Zrs are more used to touch screen, maybe they should invent a touch screen interface that you can use with the computer, maybe even incorporating the mouse somehow.

For me personally the touch interfaces right now are fucked up - I always tap the wrong letters on my phone, the auto-correct and suggestions used to compensate for this often times make it even worse, and swipe doesn’t come up with the words I want, I often have to swipe multiple times. I can’t imagine operating a computer like this, but maybe for Gen Zrs it’s no problem.

Maybe in the future you just need to think the word and it appears on the screen, and typing would be obsolete.

For a distributed database there is also fragmentation/sharing though. In this case calling the nodes replicas is not accurate. I guess you would call these “shard” or “dsta” nodes.

You are right about the “slaves” not behaving, in fact they jump on the chance to become the “master” themselves once the current “master” goes down. Then there is the split-brain problem.

It’s really more like a worker boss relationship, but I would hesitate to call database nodes “workers” because this one is usually used for a processing engine like Spark.