Elm vs Assisticant architecture

As you can tell I'm just snooping around your repos for interesting things. I've never looked at the Elm architecture... does it differ from standard MVC?

There's a UI architecture that I immediately loved, because when I discovered it around 2010, I had been thinking along similar lines for years but hadn't been able to figure out exactly how it should work. I first saw it in a library called [Update Controls](https://updatecontrols.net/cs/index.html), which the author eventually replaced with a similar thing called [Assisticant](https://assisticant.net/). This is similar, but different, to the architectures in JS libraries like MobX and Vue3. To be honest I've never been a fan of MVC, and I don't see why people would choose it over something like Assisticant. But to have made this repo, you must be a fan of Elm's version of MVC, so I'd like to hear your thoughts and what you like about it.

The issue names no files, tests, or entry points. It asks for an architectural comparison between Elm, MVC, and Assisticant rather than a defined repository change; completion would require an agreed explanation or documentation scope.

Written by the indexing model from the issue text.