OpenAI already logs everything you do with their service, and this keypad can only be used with OpenAI.

I doubt that seriously. The big Iberian Peninsula outage already mentioned happened because a "reliable" power source was not decoupling correctly from the grid. France right now runs into electricity problems because its "reliable" nuclear reactors have to be shut down because of excessive heat making the cooling of the reactors problematic.

Your "reliable" power sources are not reliable, they are inert. This is not the same, and if conditions change quickly, or aren't within specifications, they fail in a big way.

Exactly. But you have to keep the original BSD license intact. You can modify the files, but you have to acknowledge, that you got them from FreeBSD. That's why many commercial companies like to base their systems on FreeBSD.

Which might be true for the Southern U.S. states, true.

On the other hand, we tried this in the 1970ies already, and it was abolished immediately after the first winter, after traffic accidents during morning rush hour had risen sharply, and school children had to wait for the school bus in the coldest time of the day (and the school bus took longer because of all the icy roads anyway).

That is not true. Left without clocks, humans in median latitudes tend to sleep longer in winter than in the summer. A standard schedule throughout the year is not healthy, except you live close to the equator, where the day length does not vary much during the year.

It's not only that. It's more that then, the very short daylight is concentrated in the evening, because you get up an hour early, during the coldest period of the whole day, and then you are wasting the daylight in the afternoon, when it is too cold anyway to have any outdoor activities which could profiteer from the light.

Not having DST, especially in regions away from the equator, is also dumb. You have to deal with the fact, that the Sun rises in the summer much early than in the winter, and getting up in total darkness and not having any daylight until late in the workday like DST in the winter is as annoying as trying to go to bed when it's still bright outside.

So either you abolish a strict day schedule and adopt during the year, which is not only two switch days a year, but multiple times, or you have some kind of switch between Summer time and Winter time.

If the Netherlands did this, they would reverse it immediately after the first winter. Not getting any sunlight until past 10.00 AM is so annoying, and the cost of road maintenance because rush hours is when everywhere, there is still ice on the roads, will be prohibitive.

People complaining have simply no clue how it is to have DST in the winter, and can't imagine.

We expected them 20 years ago, when all people working in the field knew already that SS7 needs security safeguards, not to sit on their hands and do nothing.

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.

Most of the population of Alberta lives south of the latitude of Hamburg, Germany. In fact, Edmonton is on the same latitude as Hamburg, where my sister in law lives. And she has Solar on her roof and generates about 70% of her own electricity. I don't see your problem.

No surprise here. Many important molecules for Life on Earth are quite abundant in the Solar system, especially in the icy worlds of the outer Solar system. It would need some serious scientific argument to rule this out for other planetary systems. Now we have proof that at least the building blocks for Earth-like lifeforms can form spontaneously anywhere in the Universe. No panspermia or other wishful thinking based theories required.

We all know that a mouse moving in a perfectly straight line means a machine is controlling it [...]

Unless your mouse has angle snapping or is a wireless mouse and there is movement lag because of interference.

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.

There are regulations nevertheless. The limit is 8 hrs of consecutive driving, after which a 30 min break is required, and 11 hrs of maximum driving after an 10 hrs break. It would make sense to split the 11 hrs into two 5-6 hrs periods with the 30 min rest in between. With 60 mph, this gives a driving range of 360 miles on a charge. A commercially available Mercedes eActros 600 with 600 kWh of charge would easily be sufficient, requiring a 30-80% charge within 30 mins. Or you go for the 14 hrs total, and split the 11 hrs of driving into them, giving you for instance a 3 hrs drive/1 hr rest rhythm, and requiring you to recharge for 180 miles during the stops, which means that you could drive that schedule by charging solely at 350 kW chargers.