The algorithm seems to have been failing to scale correctly, yes. On closer inspection, it looks like the billing software treated the bytes used as K used.

Did AWS use Grok to generate the billing sheets or the code for handling billing?

I'm serious. The errors reported look suspiciously like AI hallucinations or a signed integer being treated as unsigned.

He's creating a "middle class" - they will get the info after the regular insiders, but before hoi polloi.

He should have thought of selling multiple levels of higher tiers.

For a small fee you can get your bullshit before everyone else.

That's not an argument.

"Yeah, that guy is dead now. We have a pretty solid idea who did it. But not sure if that'll make him alive again, so let's not bother with catching them."

I should have added:

"In general, renaming things does not fix a problem."

Though heaven knows, lots of stupid people try it.

Why not just discard the whole idea of DST instead of putting it into permanent effect?

The whole concept is an attempt to redefine time as a way of addressing perceived social problems. Schedule activities around the clock, not the clock around activities.

Not surprised that someone exploited a vulnerability, but surprised that deployed military personnel are allowed to use civilian communication systems.

Good question. Their POWER series of CPUs were not insignificant in capability, their chip designers were clearly technically sophisticated, and GPUs are just specialised vector processors with a few extra bells and whistles - stuff IBM is extremely familiar with.

It would not have been difficult to release a GPU or other LLM-specific processor to go along with the POWER11. They'd been working on the POWER11 for 4 years, they knew in 2020 that LLMs had a strong potential to be significant for Big Data processing - an area you use big iron for, they're not rank amateurs, they have plenty of reserve, they could have assembled an emergency team to build a vector processor that was custom-designed for just LLM work, and released an LLM processor card that could run circles around nVidia.

They didn't. Because, as has happened before, their management is simply too stupid and too slow.

Your link - seriously?

"Tobacco giants say"? Dude, they said that smoking is actually healthy for a few decades. I'd trust my cat around buckets full of her favorite treat more than those companies.

I keep hearing things like "my grandmother got so confused, I set her up on Zorin/Mint and she couldn't tell the difference."

The more people just use their PC's to get on websites the less they seem to notice if they use Windows or Linux.

It doesn't matter if it's bad - if China and Russia agree it's bad you have to be for it.

You can never agree with China because they have a totalitarian AI Surveillance Police State there so you must support a totalitarian AI Surveillance Police State here.

If you are against techo-feudalism you must be one of them Putin Lovers.

- The New York Times / Langley, apparently.

I'm amazed to find your comment is an isolated example of reading comprehension and critical thinking.

Many others are 'accepting the premise' and 'entering the frame' of the LA Times weirdos.

Didn't expect that today.

What if...

Someone (say someone who was familiar with doxygen and GCC) developed number of comment types, where some stipulated preconditions that must be true for the function to run correctly, postconditions that must be true once the function has run, kernel facilities that the function definitely needs, and kernel facilities that the function definitely doesn't need. These would all be optional for any given function.

A static checker could then validate if the code meets the behaviour expected by the programmer. This is precisely what is done in SPARK, a fork of Ada for high-reliability code. Combined with existing static checker capabilities, this would greatly increase the number of bugs that could be caught with all kinds of tools, AI included.

It could ALSO build a full fine-grained mapping for any fine-grained mandatory access controls system. You'd also want includes that you could import for precompiled libraries. This would allow someone to verify if the code was making unanticipated/undesirable calls but would also make SELinux possible to develop for at the application level.

It would not be trivial. If it was trivial, it would have been done simply because it already IS done in other languages and that makes it "obvious" to anyone who has been programming for a while. However, it should not be massively complicated, simply because you can use AI as the static checker. Once it has a definite set of bounda that must be satisfied, it should be much more capable of knowing what paths would violate those bounds. Which means that the checker stage essentially is trivial today, leaving only the markup stage.

Because the cost to society is paid not by the smokers but by all of us. And health care costs are only the tip of the iceberg.

There's no culling here. Both doom scrolling and smoking kill you so slowly that evolutionary it doesn't matter.