Indeed not coming from nowhere! Visual Studio Code has been a success given the widespread adoption by developers and plugin makers. Fluid components seem a powerful and worthwhile concept as well.
It reminds me of the "dynamic emails" Google is sending with up-to-date overviews of Google Doc comments at the moment you open the mail. It would be good to open up that tech.
At the same time, people are solving this problem already by sharing links to some tool with realtime collaboration, instead of sending static documents. So the difference is not huge, the integration will just be better.
Or am I wrong? This was an interesting bit:
‘What if we built every experience on top of a data structure that was inherently distributed?’
I'm wondering whether they're talking about Conflict-free replicated data types. In that case, will these components offer local-first distributed data? Or will they be centralized, like most collaborative services now?
Indeed not coming from nowhere! Visual Studio Code has been a success given the widespread adoption by developers and plugin makers. Fluid components seem a powerful and worthwhile concept as well.
It reminds me of the "dynamic emails" Google is sending with up-to-date overviews of Google Doc comments at the moment you open the mail. It would be good to open up that tech.
At the same time, people are solving this problem already by sharing links to some tool with realtime collaboration, instead of sending static documents. So the difference is not huge, the integration will just be better.
Or am I wrong? This was an interesting bit:
I'm wondering whether they're talking about Conflict-free replicated data types. In that case, will these components offer local-first distributed data? Or will they be centralized, like most collaborative services now?
I love, love, love that Microsoft is making major contributions and changes to the open source community.