i.e. one of the fastest consumer machines around. I wonder how much the web would be better if more people targetted a $300 laptop instead of a $3000 one. Or probably a $30 Android instead of a $1000 iPhone.
Hmmm would be interesting to do the benchmarks on different machines and see if you are right.
There needs to be concerns beyond pure speed and package size to dictate tools. Sometimes real world practical constraints must be considered
It sounds like you're saying that the way out of tech debt is to install more 3rd-party packages and/or hire more people, I hope you meant something else.
I use and recommend React at work because of the hiring thing, but for my own personal projects I stick with Mithril. With JSX it's not hard to switch back and forth between the two, at least with TypeScript there to tell me when I accidentally use HTML in my React JSX, e.g. the class attribute when React wants the className property. (With Mithril you use attributes that map exactly to HTML attributes)
As for hiring I agree somewhat but anyone with a couple of years of front end experience should be able to pick it up in a matter of hours.
My only annoyance is that I've grown accustomed to making micro components with React, Inferno, and Mithril on the same file. Stuff like buttons and such. With Svelte (and Vue when using SFC) you need to create each component in its own file which becomes tedious for more complicated views.
> that’s going to be painful when I want to filter a live search result page with more than a just few results.
I'm using it right now with a gallery of about 2000 items with filtering and search. No problem on an i5 desktop.
Another huge benefit is that it simplifies you application code immensely. Your store and models are simply vanilla JS since Mithril doesn't have reactivity, observables, etc. Mithril will simply redraw all the vdom whenever a user event happens or when its router/http client do something. You can also call m.redraw() if you need the UI to update if you for example receive something from a web socket.
Obviously with this approach the performance cannot be as good as something like Svelte or Inferno, but it's significantly faster than React.
https://krausest.github.io/js-framework-benchmark/current.ht...
Personally I use it with JSX since I can't stand the hyperscript notation.
It's certainly not for everyone and all use cases but I think it's totally valid for a good portion of front end work if you can handle a double edged knife.