Sounds more like a quick response to the news that Microsoft is building Office on RN.
That would also be the day that I stop using MS Office as my go-to.
Because the performance was just not good enough.
They had custom, native UI while the backend was running in Java.
And it just wasn't fast enough. Even when hot, throughput and latency weren't good enough.
So, they started moving to C++ as much as possible, as fast as possible. By now you can run Writer without Java at all.
Current JS runtimes are all slower than HotSpot.
Yet somehow we're to believe that doing the exact same mistake again will work better this time?
It'll still end up being slow and a memory hog.
Moore's law is dead. RAM is more expensive than at any other point in almost 10 years.
You can't just throw abstractions at everything at the cost of performance anymore, expecting the hardware to catch up.
Somehow I got the feeling that MSFT has been invaded by JavaScript developers.
Working in C# on .net 4.5-4.7 is such a tremendously productive platform.
It appears it is the usual political issues between Microsoft divisions, which I thought had gotten better after all the re-organizations that took place.
I wouldn't be surprised if this JavaScript everywhere wasn't yet another way Microsoft is trying to appear cool among the Google devotees crowd, like how they are jumping in PWAs as well.
Microsoft is as relevant as ever outside SV coffee shops.