When I say be careful what you wish for, what I mean in this instance is BE CAREFUL WHAT YOU WISH FOR!

Do you honestly think the bottom dweller portion of the base is going to know the difference or care whether Trump is real or an AI creation that lives indefinitely?

Could get to the point that they'll run picture-in-picture with the ad in the main screen portion and your desired show in the corner inset.

I'd vote for raise prices, as long as it's disclosed that their data mining and advertising practices will not be enforced.

Is this a case of Cyber-Darwinism?

I'm positive my stupid dog will destroy anything that gets dropped in the back yard.

For those of us who have stupid dogs that love to destroy everything within reach?

I'll let you in on a little secret: there's plenty of those in 1st world countries as well.

Considering the ratio of land to coastal regions, Europe is fairly thin. With the oceans warming up at record rates, the continent is suffering from the same fate that has plagued Florida for a long time - excessive heat.

My father was a hardware junkie and liked building computers. One of the first I got to play with was a Motorola 6800-based system (probably from Heathkit) that had a custom built CRT monitor that was 3x the size of the box containing the computer (and weighed enough to kill a small child). Everything was wire-wrapped in that day for the parts of that system. Learned how to do BASIC and assembly. Found the Motorola architecture a lot more sane than other brands. As for my father's computer, it was a ComFile 8080 system with dual single-sided 8" floppy drives and an old Teletype printer with the paper tape reader/writer. It ran a very crude DOS and had BASIC, and I got to learn on that system if I was being good and was after "work" hours. Later around that time period, we ordered a Timex Sinclair ZX81 that I could hook up to an old B&W television to play with. I had to master them all and learn how to use/abuse them before I progressed to bigger and better systems.

According to Apple's Store review guidelines, section 2.5.6, all browsers must basically be a skin for webkit, which is basically Safari.

Sadly, most tools and frameworks are also created by programmers (with the rare exception of auto-generated code, but someone is still responsible for that), so there is a fundamental problem where bloat begets bloat. It's a never-ending cycle.

New programmers are not trained on making efficient code nowadays, so yeah, they are responsible as well. They are trained to do it a certain way and not to optimize anything. They just are not able to think for themselves. The culture of most businesses does not help either. Most managers don't care either, because they hope that they can get promoted higher or escape before the shit hits the fan on code instability. "Get it done quick, since we are just the development team. Final hardware requirements are not our concern."

Standards have a role in this as well. It's all about readability - as long as the next newbie can read it, all is good. A lot of code that I've seen other people write wastes precious time and effort by not making use of how compiled code works best. Breaking everything up into discrete instructions, you lose the effect of most languages quickly reusing the same value from a simple assignment. If most programmers understood the ins and outs of how compilers (JIT interpreters or static versions) process their crap code, they could write it in a way that would allow for the same operation but with more efficiency. Sure, the code may be a little ugly, but for something that would be run millions or billions of times over the course of the program execution, it adds up quickly.

Gone are the days where programmers program based on their environment efficiently, because hey, let's throw more CPU/memory/Storage at it and pay the hardware costs. That's why/how major OSes nowadays are humongous turds that require 10GB+ just for the minimum install. In order to work with said OSes, you have to learn the crappy way to design your code, because that's how the (inept) designers wanted (inept) people to interface with it.

> Of course I want to scan a trillion items with my smartphone when I purchase groceries for the family. There's nothing else to do with my copious amounts of freetime than to slowly waddle through the dairy aisle and painstakingly scan and check each and every item, cursing twice because I locked the phone out of habit again and the in-store wifi being too slow and 4/5G being shielded by the metal siding of the building as usual.

Agreed. There is also the issue of how much time the fridge door is open at the store while some stupid millennial wants to scan with their phone instead of quickly visually scanning dates to find the milk they need to get, and that adjusts the cooling environment and screws up the milk for everyone else. It gets worse depending on where the QR code is placed on the container, whether said millennial has to take it out of the fridge to hold it just right to scan it, because of how the store staff loads it in the back of the fridge. All this means longer lines to get milk, while nitwits (conditioned to scan everything because they can't make quick educated assessments on their own in a few seconds) waste time for everyone else.

This QR code use seems like a more wasteful idea period because it will waste your time, my time, and the quality of the product all at once.

War of the Worlds... yadda yadda yadda

You and your stuff get vaporized. Who cares whether you used passwords or not, as you and your "keys" no longer exist.

Windows 3.1 had a horrible multitasking kernel. Any time you accessed a floppy drive, the whole system would come to a halt on processing anything interrupt-driven, like COM ports. Found this out when trying to write a data acquisition systems in the mid 90's. Good thing that Windows 95 (and its better kernel) came around, or we would have been screwed, because the system needed to regularly backup data to floppy disks.

What about the Minions?