Not nearly as irritating as having dozens of random dot subdirectories in the root of your home directory.

The first issue costs a few developers a few days of their time to fix. The second is a problem that nags millions of users for eternity.

Because at this rate, by my math, the number of AI cores Google requires will exceed the number of atoms in the visible universe within about 120 years.

What I typically do is leave in the no-name AAA alkaline batteries that the remote came with, and it works for a couple of years until I move on to newer gear.

Then after I've left it idle for 15 years, I'll come back and open the remote to discover that the batteries have leaked all over the inside and destroyed it.

If it was a reasonable balance of risk and payback, then they could get a private loan like everybody else.

Why should he stop exactly explaining the situation?

Lenders take on the risk of a default, and when the government lends money, the risk is socialized.

The loan is being made to a private, for-profit corporation, who will be able to keep any profits generated by this scheme (however unlikely that may be).

Whatever activity the loan is for is irrelevant, whether it's for cranking up a crusty old nuclear power plant, or for bailing out a Wall Street firm during a market panic.

That's a trick question.

Answer: None. In 2025, Everything's Computer.

Omitting the camera saves the consumer the minor cost of having to use up a square inch of electrical tape.

Show me the how you can create a system where the price totals of all possible combinations of inventory selections result in only (3 or 4) mod 5.

People need to consider: Rounding to a nickle isn't going to be greater than 2 cents more inaccurate than rounding to pennies. Let's say you live in a backwater state, and still only make $7.25 per hour. Each transaction could potentially cost you at most 10 seconds of extra wages. However, transactions randomly round up and down, so the average error gets reduced by the square root of the number of transactions you make. Statistically speaking, you'll gain or lose only a couple of seconds of your time per purchase. Probably less time than it took to fumble for all those pennies.

But it sucks to be poor. Without pennies, someone who makes $50k per year will gain or lose only milliseconds worth of salary per transaction on average.

"But the stores will set prices so that it always rounds up!!!!1!" -- That only works for one item at most. Savvy shoppers would strategically buy combinations of items that always round down.

In a few years, all of these GPUs will be available on eBay for a few bucks each.

Then I'll finally be able to snag a whole bunch of them and build a Beowulf cluster to run SETI@home faster than anybody else.

That work sounds like a great candidate to offload onto AI!

The merchants need to consider that if their competitor down the street still accepts rewards cards, the customers might just switch, and then they've just lost the whole sale. All this over a 1% extra cost to the merchant.

In the meantime, they think nothing of offering things like buy-one-get-one-free deals to lure in a few more customers.

That summary at the top of this story is just way too long. I'll have a chatbot break it down and give me the gist.

If you're locked inside an ATM, have you tried banging on the case to alert passers by?

Almost nobody uses "untyped languages". Few of those even exist, with Forth and various assembly languages being the main examples. (C, with its type system that is as airtight as a sieve, gets an honorary mention.)

You're probably harping about dynamically typed languages. In such languages, the runtime still knows *exactly* what type every item of data has. These are not weakly typed. But what you obviously prefer are "statically typed" languages.

Static typing might statistically reduce some errors, but it certainly can't "eliminate whole classes". Consider "set_warhead_target(float latitude, float longitude)". Did the type system give you any protection from accidentally swapping the two parameters? That's really the problem that you're so worried about: accidentally using the wrong data value in the wrong place.

However, very few statically typed languages (with Rust being a notable exception) have eliminated the biggest source of type errors in computing: Null, which is a bogus placeholder that matches any pointer type (or reference type, depending on the language's nomenclature). So in many cases you have no less risk with static typing than you do with accidentally feeding a string into a Python sqrt() function. And in the case of C or C++, you can be much worse off, as in segfaults and remote exploits.