My personal experience is like getting eye glasses for your appetite. Easier to eat reasonably sized portions and they're nutritionally well-balanced.
Also the late night cravings are more specific: instead of vague "need to eat something", it's "I'd love a tomato" or "mmm yogurt" or "actually a load of carbs would hit the spot".
55 C might be enough to heat buildings but it's right on the edge where domestic hot water needs to be to kill Legionella. So traditional DH systems need to run hotter.
There low-temp/cold DH systems out there that rely on heatpumps in the buildings to extract the heat. Less losses in the network and you can even use them for cooling, but needs heat pumps everywhere.
In comparison, a traditional heat exhanger is pretty simple technology; just a hunk of metal with a valve.
Microsoft's already building data centers hooked up to district heating (Espoo and Kirkkonummi, Finland). Heatpumps are amazing.
(Seasonal heat storage is also a thing, Espoo's neighbours have tens of GWh of storage, with a new 90 GWh cavern in the works. Not sure if the systems are interlinked.)
And then there are us engineers. I don't care much either way whether Maxwell's equations are ∇F = J or some other form, as long as it makes the problem easier to solve.
If I were in the GA Marketing Committee I'd publish a paper with suitably hand-picked worked examples where the vector approach is long and tedious, and GA version is short and sweet.
They're not great for anything that might produce heat. Seeing a MOSFET slowly starting to imitate the Tower of Pisa after dissipating a measly 1 W for a few moments was a sight to behold.
One of these years I'm going to make a Finnish programming language that enforces the correct case in arguments. And I don't mean silly arguments like camelCase vs kebab-case, I mean grammar.
Some examples to illustrate:
tiedosto on "foo.txt" avattuna
tulostin on PRN1
kirjoita(tiedostoon, "a")
kirjoita(tulostimelle, "b")
If there were one. The closest thing is the Treaty of Lisbon, which in turn was an update on the Treaties of Maastricht and Rome.
However, the matter has been heard in the European Court of Justice in 2002, and the short version is "Community law does not preclude compulsory military service being reserved to men."
Humbug. Defence policy, especially how the EU member states choose to organize their military forces, is very much in the hands of the individual countries. A majority of the member states don't even have conscription anymore.
Yes, there is the common security and defence policy, and the Article 42 of Lisbon and all that, but it all still relies on national systems.
I couldn't let this be, so I went through the commits and as far as I can tell, that's the case. The committer/author names and timestamps are consistent with using --author on a commit (... or in a few cases, --amend --author).
Except one: commit 3d1fdddf9 has Jia Tan as both author and committer but the author timestamp is in +0300 while the commit timestamp is +0800.
UTC+2 isn't very convincing as an argument for Russia. Only the Kaliningrad exclave uses that timezone, and if I were in a state-backed group, I'd live in one of the big cities.
Also quick search suggested UTC+3 was seen during the summer, and Russia doesn't do DST either.
Edit: some of the UTC+2/3 times are attributable to being differences in git committer and author dates (e.g. email patches)
Also the late night cravings are more specific: instead of vague "need to eat something", it's "I'd love a tomato" or "mmm yogurt" or "actually a load of carbs would hit the spot".