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.

I think they feel it would be more like humans communicate. But humans invented blackboards and certainly found them useful to improve communication.

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.

More than 35 years ago, well before the Internet, BBSes ruled.

One I was a pillar of was nothing but a wall where you would post anonymously (or not).
The software was written to verify the typing rate to make sure that no text was uploaded

CHALLENGE ACCEPTED!

I wrote a special terminal program that would randomize the time between characters to foil that BBS's rejection of uploads...

(Oh, it worked, and the dude running the show never found out).

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.

It's a trade off: you get abundant free energy to run the server, with extreme constraints on cooling because your server is running in the most perfect Thermos bottle ever.

Others are taking the opposite tack: undersea data centers for abundant free cooling at the expense of having to get the power down to your servers.

If had to bet on which one is more practial, I'd go with undersea servers. Build them off the coast of Chile, run cables out from batery-backed solar plants in the Atacama desert.

I'm having a bit of trouble working up any sympathy, as the saying goes.

Is to set coursework and exams that are specifically crafted to exploit where AI is weak or prone to hallucinate.

You do not ban cheating, because those who cheat will inevitably find ways to circumvent the ban.

Rather, you exploit the properties of the mechanisms of cheating to ensure that those who actually understand the ideas are marked relatively highly (regardless of whether they reach the textbook conclusion) and whose who do not understand the ideas cannot do well even if they give what is in the textbook.

The interest should not be in precise answers, but in precise use of tools of reasoning and analysis, because this is what actually matters when it comes to understanding. Yes, it means you can't standardise so easily, and you have to devise things in ways that don't penalise intuitive thinkers over methodical thinkers, but you cannot teach a subject properly if you are only concerned about the surface.

Facebook is not in chronological order.

The FSB is certainly getting a good ROI on their investment in Trump.

I didn't see a 5.6 option on the Windows client last night.

Haa anyone else observed 5.6 in the wild?

Trump doesn't need to have power, he only needs to create fear, uncertainty, and doubt.

Companies are risk-averse, which is why Anthropic pulled their AI model for a while.

People do not tell the truth about their motives when answering polls. News at 11.