fusionjs VS Mithril.js

b) Don't do intermediate builds at all. This is what we do for monorepo-internal packages at Uber. Basically, our framework lets you specify what parts of node_modules should be transpiled when compiling the service. So basically you just have a single compilation step and the performance cost is alleviated by leveraging babel cache. The upside of this approach is you only need one file watching daemon and you don't need to worry about BS related to intermediate compilation bugs, NPM publishing interface, etc.

I also worked on another framework which does ship with polyfills, but this one is very much a "we-call-you" framework, in the sense that it has an full-fledged, opinionated compiler with hundreds of hours worth of time spent on optimizations, and the inclusion of polyfills is also very much a deliberate choice made in the name of productivity.

We've gone down this rabbit hole with Fusion.js. The TL;DR: is core.js aims to be standard-compliant, which means it'll often pull in a lot of code to deal with obscure corner cases like dealing w/ Symbols.

At work we use another framework called Fusion.js. One thing that we find important is its plugin system, which allows colocating server/client/hydration logic by concerns, rather than by environment, meaning we could enable/disable, e.g. Redux hydration by registering a plugin, rather than peppering redux code in a bunch of disparate lifecycle hooks.

I don’t enjoy React much, but (as I’ve commented before) I do love Mithril (https://mithril.js.org). Immediate-mode UI via a vDOM, like React, but small, simple, and with none of the reactivity complications. I’d never go back to building apps with pure JS.

You can find more information about Mithril.js on its official website.

The idea of nested function calls to build HTML is not new. Back in the hey-day of JS frameworks, this was a common vdom pattern. I kinda miss [MithrilJS](https://mithril.js.org/#dom-elements)

I have mixed feelings about React. I like it better than jQuery, and better than other JS frameworks I’ve used.

But I much prefer Mithril (https://mithril.js.org/), which offers the same immediate-mode advantages (https://news.ycombinator.com/item?id=19746235) but without the crazy complex dependency-tracking reactivity.

I rather liked this comment on React: https://news.ycombinator.com/item?id=38640051

Vue with Vite (the builder/runner) is a stable, open source option. It is really a lightweight start where you're mostly writing HTML with interpolated data, and Vue is updating values correctly and performantly. Just build your reactive HTML app in one file and break into separate components as you're feeling the spirit. https://vuejs.org/guide/quick-start

Mithril if you just want to drop in want a tiny, complete reactive library that doesn't require a build step--this one is most like what you might end up creating in a large jQuery app. You can understand everything from the homepage. https://mithril.js.org/

HTMX if you really like HTML conventions. This doesn't feel jQuery-like and depends on your approach to your server app. https://htmx.org/

React is still has gratuitous complexity. If you need some React like, take a look at mithril which is simpler and much smaller.

The submitter creating multiple var -> let PRs (one PR per file), was also doing this in other projects, and would've broken some of their users.

https://github.com/MithrilJS/mithril.js/pull/2880#pullreques...

And he created multiple PRs there too. And didn't follow their workflow...