[gigel82]

Which looks like Quip, which looks like OneNote, which looks like a million other note-taking apps before it.

I think the more interesting aspect is the extreme coauthoring; it looks like the underlying tech is open source as well which is pretty interesting for a lot of applications: https://github.com/microsoft/FluidFramework

[AlanYx]

The similarity seems more than skin deep though; the "Loop components" data model as it's described in the linked article sounds similar to the underlying data model in Notion.

Notion doesn't have the multi-cursor live coauthoring feature though; that's new.

Do you know if the Fluid Framework is built on top of CRDTs?

[gigel82]

Didn't do a deep dive, but it looks like they have distributed data structures (DDSes) on that layer, which appear different to CRDTs (merging on the client, not on the server).

I can imagine someone could build a multiplayer game on this thing (though I doubt that's what MS designed for).

[WorldMaker]

From what I recall of a BUILD talk once on the deep dive fundamentals, Fluid is based on CRDTs under the hood (or possibly the CRDT predecessor OT like Wave was), but Fluid believes writing CRDTs is hard (it is), especially writing them that obey the math laws CRDTs are supposed to, and then getting that to perform well (including and especially things like catch-up/replay) is also hard, so yes the actual programming interface Fluid presents is high level "distributed data structures" though the wire format is closer to CRDTs with some cheats from assumed knowledge of the data structures (things like sending the latest contents of a list for catch-up rather than replaying the entire CRDT chain for that list).