Comment Re:Worthless fucking statistic. (Score 1) 27
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.
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.
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).
Permanent standard time is ideal for human health and balance of daylight throughout the day.
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.
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.
People complaining have simply no clue how it is to have DST in the winter, and can't imagine.
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.
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.
German YouTuber Elektrotrucker does international hauling throughout Europe for more than a year now, and he regularly recharges at a normal car charger.
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.
If you're not part of the solution, you're part of the precipitate.