You haven't worked much as a developer. Having built systems used by tens of millions of users I guarantee you that every time Amazon rolls out an update to the store or cloud software there's an ops person biting their nails hoping the system doesn't die. When Google released Gmail they only allowed each user to invite a certain number of friends in order to slowly ramp up the system. Writing any software that is made to have millions of users on day one is really fucking hard.

On top of that steps 2 and 3 require interacting with external systems who may also not be able to handle load well, and probably use a combination of buggy and poorly documented interfaces, and step 5 requires reading a bill so long that the people who voted for it didn't bother to read it. You're grossly trivializing the problem.

It's worse than that. Large companies will lobby government to make sure that not only government contractors must be certified on the standard, so must anyone who sells to certain regulated industries. Want to sell to airlines or food processors, even if it's non-critical software? Hope you're certified.

It's cheap, and no matter how crappy a job the builder did on your subfloor the carpet will not crack when the boards start to move apart. It also absorbs a lot of sound and causes less injuries when the kid falls down the stairs.

The only places you need quick-charge station are places where people will be traveling long distances. Most of the time people will charge overnight at home. Most highways have areas where you could easily build a huge lot with rapid chargers. I suspect the larger issue most places will be finding and transporting enough power to charge perhaps hundreds of cars at one time.

Google 'free fax'. There are plenty of companies that will fax a PDF of a couple of pages for free.

Perhaps they are exploiting security holes in current versions of Java that are due to be patched soon.

Does nobody do signing or encryption of signals to control systems? Having had issues with VW's electrical systems in the past I wouldn't blindly consider a more complicated setup to be a benefit from them.

It's a bug, but some people rely on the current behavior, so the next release will have RealSpecificationFormal that does more what people might expect.

If you've in an area of the world where they grow tobacco people smoke, third world or not. Same way third world countries with poppies often have some level of opium problems. Drugs are cheap if you can produce them yourself.

On the ground this could be easily solved in a number of ways. When a plane goes off-course where it shouldn't be, however, the last-ditch attempt to communicate by the fighters that intercept is a standard set of hand signals. That could be a problem if they can't see the pilots.

Windows screw up the aerodynamics and force the cockpit to be at the front of the plane, making the most critical controls run the full length of the plane. If the front of the plane were smoother a flight could burn less fuel, the main cost in flying these days. If the cockpit were towards the back a lot of weight could be reduced in control lines to the wings and tail, all that's needed from the nose is wiring for a couple (critical) warning systems.

The post-2000 revival of apple, sure, that was Jobs. But the founding and initial success of Apple would not have happened without Wozniak.

SCTP already exists, and is reasonably well supported. No one uses it because it turns out TCP and UDP actually do most of what we need pretty well.

You need to be out of the controlled airspace for the airport. Or you need to have ATC approval for where you are. Same as every other plane in controlled airspace.

Actually, if you want to fly an ultralight aircraft and keep it below 1000ft you may not even need the license or certification, depending on where you are.