This is just naturally solved by capitalism, no magic.
When electricity on the grid is cheaper, all intensive applications can run at that time.
Just make the difference of price worth the pause of the industry when electricity is scarce.
Realm Sync, Mongo + Kotlin MP will cover basically all platforms (server, web, mobile, desktop)... at a cost. Actually interested by alternatives.
Will this be part of your article?
Yes the Storm was horrible and the Torch was just ok.
But Blackberry 10 didn't come that late. At release time it was superior to the current iPhone and Android in many points.
Usability, dynamic permissions, the Hub, animations were so fluids and responsives, virtual keyboard, advanced dev toolkit...
It was one single thing that killed it: Customers were told Blackberry is old and un-cool. So they think.
But this xan be be a. ery good complement to an actual layer.
The layer would spend less time preparing (so cheaper) and will basically direct the IA and act as safeguard when the AI gets so confidently incorrect.
This medieval example sounds like an easy shortcut though.
At part of Europe, roads were always maintened. Maybe with more local that country-wide focus sometimes.
The feudalism may not caused by road system efficiency. Good roads on a empire splitted by succession are still no match to fast manoeuvrable drakkar raiders.
Local power and defence is needed... leading to another important parameter. Size of empires is proportional to time of travel and relative defensive strength of the remote area.
I guess the distance is also proportional to the strenght of the remote part and the brutality of a vengeance from the capital.
England, Fance, Spain, Portugal keeping colonies for a while until they technologically matched and that enlightened europe would be less tolerant of a bloody revenge.
Russia, China still controlling their colonies because there is no local comparable strenght in those moutain/toundra/desert parts.
It seems to be the most accurate choice to answer the described needs while solving the lack of native dependency that QT is apparently facing.