In my state in the US, they started differentiating between a "supply" rate, as in who generated your electricity, versus a "delivery" rate, or who delivered the electricity. That way they can market the supply rates to you and charge you on delivery additionally.
That sounds a little complicated, do the two parts actually adjust dynamically?
In China, end users pay a single bundled retail electricity price that already includes the full cost of both generation and delivery. The State Grid company purchasing electricity from generators and settling with them centrally.
Electricity prices are also government-regulated, and any change must go through public notice and approval.
This is particularly nice when you're warming the car up in the garage during cold snaps. Hard to do this with ICE vehicles without risking carbon monoxide buildup.
For readers wondering, OpenRouter isn’t capable of caching as effectively as DeepSeek is because they will, for instance, switch inference providers in the middle of a session.
How can they? If you use openrouter Deepseek fine but can’t you select the model direct from Deepseek you’re basically getting api access models that way.
Deepseek is cheap and fast, but it couldn't follow the basic directions I gave every other model (GLM, Qwen, GPT, Claude) to use red/green TDD. Put me off of using DS.
The UI design gap is something I’ve noticed as well, in things as simple as ASCII diagrams. Claude has a more human touch. All the diagrams GPT 5.6 generated for me were dressed up lists with too many pipe symbols.
> "Quite frankly, the biggest issue we are now having is not a compute glut, but it's power and it's sort of the ability to get the builds done fast enough close to power," he told the show's hosts. "So if you can't do that, you may actually have a bunch of chips sitting in inventory that I can't plug in. In fact, that is my problem today. It's not a supply issue of chips. It's actually the fact that I don't have warm shells to plug into."
