At my job people discuss almost weekly what the best models are for various price/quality points, with our CTO in particular wanting us to make sure we're being cost-effective in terms of what we're using for a given task (his words are basically "I don't want you to use these tools less, I just want you to use them effectively")
Your only talking about variable direct energy. Does it take into account the entire lifecycle, building the data centre, running the cooling, building the chips, the % the chips are not utilised.
> Does it take into account the entire lifecycle, building the data centre
My entire point is that 99% of the dollar cost of running these models goes to things other than the GPU power. The capex cost to building cost to GPU cost to storage/networking/chasses/wiring plus the other operation costs dwarf the electricity. Even the other electricity costs, lets say double it for all the supporting compute, plus another 25% for a 1.25 PUE, and you're at 2.5% of all-in cost of running these models is from electricity.
The non-electricity costs are massive and the constraints on fabs, etc. will drive the amount of the AI build far more than energy availability.
The thing I like about Svelte the most is that it's closer to raw HTML. Rather than having to keep up with all the React developments if you're not using it all the time.
yes! I learned React first, and then Svelte. Svelte seems to have all the benefits without any of the React abstractions that are more pain than they’re worth.
Is anyone hand-writing code anymore though in 2026? I don't think many people these days have to worry about "keeping up with all the React developments", because Claude/Codex handles all that now.
Yes. I can understand a backend engineer who wants to slap together a frontend just deferring the whole thing to LLMs but there are a lot of frontend engineers out there that care a lot about performance and the like who are absolutely keeping up with React developments, no matter whether the final code is LLM generated or not.
There's not really any way to make a website look exactly how you want it to look without manually fiddling with its HTML and CSS. I took the agent pill as soon as I could and never looked back, but it's truly much more work to ask the model to make small changes in natural language, observe, and iterate when you can just open the developer console and do it yourself. That said, I modify the site by hand only enough to get it into a state where I can dump it on an agent to finish up.
I handwrite plenty of code. I know what I want the thing to do, how I want it to behave, or how I want it to look; the LLM can't read my mind and doesn't get it all the way there.
To quote Mordin Solus: "Had to be me. Someone else might have gotten it wrong."
reply