As Wikipedia says, "some official plugins proprietary". So "can be" is doing a lot of work in that sentence. I would at most compare it to saying that VS Code is open-source.
It's probably more correct to say that there are some people who project that 240GW of additional power will be required by data centers in the near future.
Yes, that number is absurd, and data centers will certainly need to make do with less, regardless of actual requirements.
That also fails to take efficiency and cost optimization into account.
Just parsing out salutations and please/thank you from AI requests reduces utilization and that’s not really even intense optimization.
Earlier today on the radio I heard Houston TX was 20 GW at peak load.
Texas is [d]oing its best to build as many datacenters & power plants as possible. They were describing it as "Texas will have more datacenters than anyplace else in the world." This was public radio, but everybody's taking a hit on the ol' AI pipe nowadays.
I’ve never thought of it in terms of “how many new metropoli(sp) are being added”, but it seems like a deceny unit of measure. If we use the average of 6gw, we’re adding essentially 40 nyc’s.
That just moves the problem to the GLFW maintainers. The point is that the Wayland designers should have learned from the mistakes of 40 year old APIs, but they are not only repeating the same problems, they made it even worse. That's quite an achievement tbh.
I am too lazy and not enough of a snob to write several paragraphs on why Aeropress is objectively better and different from French Press, but it is, and I hope someone can step up and do that here.
It's just the "dev kit". Snapdragon for the laptop form factor is alive and well. You don't need a devkit for a laptop running Windows and QCOM easily figured that out.
