FluidFramework VS med

Have you seen FluidFramework? It's open source (MIT): https://github.com/microsoft/FluidFramework

I think the first product they're building on it is Loop: https://www.zdnet.com/article/microsoft-introduces-loop-a-ne...

Full disclosure I work at MSFT and on the fluid framework.

If you are interested in this you may also be interested in the fluid framework, https://github.com/microsoft/FluidFramework

We use websockets and solve a lot of the state management problem called out here by keeping very little state on the server itself. The primary thing on server is a monotonically increasing integer we use to stamp messages, this gives us total order broadcast which we then build upon: https://en.m.wikipedia.org/wiki/Atomic_broadcast

Here are some code pointers if you want to take a look:

The map package is a decent place to look for how we leverage total order broadcast to keep clients in sync in our distributed data structures:

(Disclosure: Work at Microsoft, but I work in Azure and some open source stuff, not on or directly with Fluid/Office/etc.)

That's just a trademark clause for Microsoft logos and brands. The Fluid Framework itself is [MIT licensed](https://github.com/microsoft/FluidFramework/blob/main/LICENS...) and doesn't require exposing any of those logos/brands when you use it, so the framework itself is fairly open for usage.

I think the main thing that would slow down adoption for Fluid is that the only "production" backend is an Azure service, which isn't part of the open source Fluid Framework. [Other open source backends](https://fluidframework.com/docs/deployment/service-options/) aren't recommended for productions. Until there are some open source ones, I'd assume adoption will be limited to folks in the Azure ecosystem.

Within the context of the Microsoft-verse, Fluid Framework (https://fluidframework.com) is supposed to be solving similar problems in web apps, although I haven't personally played with it.

Microsoft recently open sourced fluid framework. It is a distributed, consensus based, real time collaboration framework written in typescript. Fluid would keep your clients synced up and your server code would only have to handle when someone hits submit. Fluid Framework

The official documentation and the github repository seem clear.

Here's another one with a very small footprint:

https://github.com/DigitalMars/med

It's the one I use every day. The executable on Windows is a little over a meg. It also works on Linux and Mac.

I fixed my editor so that it recognizes URLs, and underlines them. Clicking on one brings up a browser on that site. I should have done that 20 years ago.

No special syntax is required. It just works. I've since been adding URLs in comments all over my code, for references. It's marvelous.

It could be extended to recognize filename.jpg and filename.mp3 to display or play those files, too. Again with no special syntax whatsoever. It just works.

https://github.com/DigitalMars/med

I still use microEmacs, which floated around the intertoobs in the 1980s. Of course, I've modified it substantially over the years, most recently adding color syntax highlighting and Unicode.

D version:

https://github.com/DigitalMars/med

C version:

https://github.com/DigitalMars/me

The "extension language" is it's so easy to just add some code and recompile it, there's no point in adding an extension language.

I like microEmacs a lot because I can use it remotely over a tty interface.

Doing one yourself is fun. MicroEmacs drifted around NNTP in the 80s, and I snagged a copy and began modifying it to taste. I've been using it ever since. The latest version was ported to D:

https://github.com/DigitalMars/med

It's a very easy editor to understand and extend.