I suspect you are right, but it is getting really difficult to tell the difference between AI and someone who simply don't know what they are writing about.
The power density has been steadily increasing over the years, and then going from CPU to GPU makes it even bigger. This wouldn't be such a big issue if they actually took the time to build the infrastructure. But nobody has time, so it is gas turbines and evaporative cooling, and that makes a horrible neighbour.
Nah, "selling shovels" is mostly a metaphor, the amount of iron that went into mining equipment was insignificant, beyond some local demand peaks. The majority of the business was consumables.
A key thing to understand about the gold rush is that it was not a major economic event, or at least nowhere near as big as the participants thought it would be, hence the tradegy.
The AI gold rush is different in that there actually is a mountain of "shovels" large enough to flood the global market quite severely.
You "suspect", but your suspicion comes with a unit of energy, which simply does not make sense in the context. The rest of us are talking about effect.
First thing missing from this "article" is a number indicating how many people don't want AI datacentres anywhere. You can't claim that someone is a NIMBY if their stance is that the damned thing shouldn't be built anywhere.
I would say that this is a joke, someone made a wobbly UI, isn't that funny. But I get a bit worried when trying to gauge much work went into this that is not required for the joke. It looks like the author actually expect people to pick up this thing and use it, and that is kind of scary.
Yeah, one needs to understand that "unsafe" does not mark which parts of the code are actually unsafe, it simply marks parts where the compiler ignores parts of its rule set. But the implications can crop up anywhere, there is no guarantee that a resulting use-after-free or similar can only happen inside the unsafe blocks.
In short, if you use an unsafe block, then potentially any part of your code is unsafe.
There is no such thing as a complete test suite, there will always be some possible bug that it doesn't catch.
In particular, if you put an LLM in an automated loop of "this test fails, please fix it", there is a pretty good chance that it will simply special case all of the tests, possibly in some contrived way that makes it not at all obvious when you read the code.
Have you actually learned to write HTML and CSS without any kit/framework?
I generally don't find that the frameworks help nearly as much as people think they do, and if you haven't learned the basics they easily get in the way of doing so.
It is the same story over and over again. Your AWS bill is "low" because the actual resources you use are a tiny fraction of what a modern computer can deliver.
This is probably fine for your case, but you could run the same load on any toaster, and without a meaningfully demanding task it is hard to tell them apart.
No, treating people with hostility and escalating the situation only makes it more likely that someone will snap and attack a cop.
People generally do not shoot at cops, because whether or not they hit the target doing so is pretty much signing their own death sentence. All cops have to do to protect themselves is to not provoke people to fight-or-flight reactions.
The whole WASM thing just went sideways from the start. It feels like the property of being practically unreadable and unwritable for humans was a design criterium, it is certainly the primary "feature" enabled by the stack approach.
Then there is the single array of memory that makes modern memory allocators not really work, resulting in every WASM compiler scrounging up something that mashes the assumptions of the source language into a single array.
I don't post often, but I think what is there is quite worthwhile. It is whatever I want to write, but topics are typically maths, game theory and cryptography. There are also a few browser games.
The site itself might also be of note to some people as an example of an extremely light hand crafted website.
Yeah, and I doubt that this is the last price hike. But I don't think this actually has a whole lot to do with ram prices. The thing is, AI cloud providers have generally been running at a massive loss, if you do the napkin maths, the procurement cost of these machines is equivalent to approximately a year of rent at these rates, for normal servers at AWS it is approximately a month.
The nature of these AIs is generally such that you can always throw more computation at the problem. Bigger models is obvious, but as I hinted earlier a lot of the current research goes more towards making various subqueries than making the models even bigger. In any case, for now the predominant factor determining how much compute a given prompt costs is how much compute someone decided to spend. So obviously if you pay for the "good" models there will be a lot more compute behind it than if you prompt a free model.