Giving out control of such things to LLMs is already complete madness, so once the first pleasure bot powered by Grok has dismembered a few thousand users, they'll get sophisticated safety mechanisms.
Though like as not you're still going to be right, after all, Stuxnet happened.
I don't relate to it myself, but I see it in people around me. It appears that's something that may not be limited to but is very prevalent in adults with very high functioning autism.
We're not that far into this new era and I already see people go back to hand-writing the important bits and manually designing their architecture because it turns out that unless you have them spit out yet another boring web app, they aren't very good engineers at all, their errors and bad decisions are very hard to predict and accumulate over time, and the resulting mess becomes unmaintainable at some point, and it appears all the harness engineering in the world can only stave that off somewhat, not prevent it from happening. So perhaps IT won't become a monoculture of agent prompters after all.
The problem is not that subtle, the only somewhat subtle point is that people don't differentiate between the datacenters of yore that were built sort of well and sustainably and the ones built in the current mad gold rush AI construction frenzy. The former aren't very problematic, often pretty good neighbors even, while the latter are nightmare fuel and will purposely not be built to be quiet and safe and stay within available energy capacity and not deplete struggling water tables, and they have the financial and political clout behind them to get away with pretty much anything. Small wonder no one wants them anywhere near them. Traditional DCs might be able to not be a nuisance despite using evaporative cooling, but no one would build that anywhere where there is a shortage of water, and the amount of heat to be dissipated by such a DC is way smaller.
But giving up a local water table might even be seen as an acceptable sacrifice, it's done for agriculture all the time, if only it wasn't done by and for the immense profit of corporations that aim to destroy all entry level jobs
and profess to be scared by what havoc their own creation will wreak, all while creating an unprecedented financing bubble.
Like, that's not very subtle at all. You can pick out some detail and try to make it about subtleties, but the larger context is very much not about subtleties.
>the only somewhat subtle point is that people don't differentiate between the datacenters of yore that were built sort of well and sustainably and the ones built in the current mad gold rush AI construction frenzy
So you're saying that all the rules and laws and best practices that HN has cheered for over the years that apply to new construction and new industry and claim to be about sustainability and environmental protections (among other things) didn't actually do what they were sold as being able to do?
Either the new ones are cleaner (I suspect they are but the difference is probably mostly on paper), or we all got lied to.
Upgrades also take time and may not be a good idea seeing how the current AI buildout is financed. There is a certain amount of capacity right now and AI behemoths have the financial muscle to take what's there. If that leaves too little for everyone else, prices will reflect that as soon as existing contracts allow.
That's not always a thing and doesn't help with fires in the rest of the complex. Backup generators, fuel depots, power distribution, large-scale cooling infrastructure all pose fire hazards even when facilities are built with actual regulation. The current AI buildout in the US happens pretty much without any meaningful regulation and gives the impression they'd build unshielded nuclear reactors serviced by children while running if they felt they could get it running cheaper and faster.
If that loud sound is roughly boom-like in shape and texture, and caused by an object moving faster through its medium than the speed of sound of its medium, then they are, in fact, the same thing.
> yq is a portable command-line YAML, JSON, XML, CSV, TOML, HCL and properties processor
reply