You may need a (screamin) front-end machine that splits up the work and hands it off to multiple multi-core machines. These multi-core machines may only be available at lower clock-speeds.

Dont just "look at your application". But look at what parts of your application are subject to parallelism and what parts must stay single threaded. You may need a special single-thread machine that can keep the other ones fed.

If we are rightly scared of browser-borne infections and intrusions, then why are we still running browsers on our machines? Why not designate a machine, outside the firewall / in the DMZ, that runs ALL the browsers. The user logs into that machine, and the browser display events are sent back to the client machine. The safe client machine never runs a single snippet of plugin, or gobbles a single byte of untrusted network traffic. The client machine does not even -know- how to get to the internet.

Sending receiving files can be locked down and logged. Or prevented.

The sound device would be a pain, and might require a new protocol, but this would solve many problems. I think it might make SSL better too (no proxy bs).

Perhaps a specialized (corporate) browser nexus product could be offered...with sound and optimized for the browser.

The client machine never talks to the internet. It just sees pictures of it.

What would it feel like to live there? Would you have to be careful walking? How long would it take to adapt.

g = 3.75 m/s^2 vs 9.8 m/s^2

Trains don't really wander around randomly. So its not necessary to use the GPS system. Fixed point emitters over the tracks using simple technology would exactly position the train and insure reception no matter what the conditions. Even inside a tunnel.

I understand that putting new hardware into the trains is hard, expensive and difficult to clear for safety. But putting new hardware into the operators hands is not. Put a friggin electronic helmet on his head with a siren that goes off if the train is too fast for its registered weight / vs the track he is on. Tell him he fired if the siren goes off.
Heck, put a tens unit on it.

I would suggest using hydraulics and fiberoptics. Dont bother with active circuits at all. If all you want to do is look and grab, go really old school. Dont use amplifiers when two tin cans and a string will survive the radiation.

They have it. We want it. Make up an excuse. Take it.

10 seconds to create a database. 10 more seconds to create an input panel that would let you populate tables with data. You could vi-edit the panels if you wanted to make them pretty. Is there an analog to that speed of development now?

The truck drives to the address or general area, and a drone lifts the package and deposits it on the doorstep. Then flies back to the truck to fast-charge for the next delivery. Short hops, with added intelligence / visualization provided by the truck.

This is but the price we pay for not dedicating an entire core to systemd. If systemd did not have to share a core with the other processes, then it would be free to seek out and steril...correct these trifling kernel issues and the ones responsible.

Why isn't it computer tampering.....tampering with a computer device or program?

Setup a hard drive or usb key with a re-installation image so that if they do experience trouble, they can just re-image their machine. All updates and software they need already installed.

Or you could have the system dual boot. Normal windows boot, but you can have them grub boot into linux and that will give you a pristine platform to log-in and save files/re-image their machine remotely via partition image. You have them boot into linux, and then you can operate on a comatose window partition without interference via ssh.

Instead of them writing AI engines to drive NPC battles, have the NPCs be human. You cannot talk or interact with the "protagonist", but you can shoot at him. Maybe by playing NPC long enough, you unlock the game and then You can play the protagonist.

I was not disagreeing with gun ownership. I just think a gun is a weapon, not a tool. If you call a gun a tool, then what is a sword? An ad-hoc non-elective surgical instrument? Overgrown Cutlery? Guns are not tools. They are weapons. I have no objection to the ownership of weapons...within reason. I just think calling them a tool seems like an attempt to shroud their importance by mingling them with other more benign implements like screwdrivers.

I am not nor will I ever advocate smart guns.
In answer to your skunk anecdote, how many rounds was your weapon capable of raining down on said skunk. If you had a gun with 12+ rounds ready fly in less than 5 seconds, then I would say you had a weapon of war.

A gun is a radically different animal. Very few tools are designed to kill people and strike at a distance. A gun is not a tool. A gun is a weapon of war that has been (barely) domesticated.