We Don't Need Faster Frameworks, We Need Better Tooling
Around ten years ago, businesses realized that building desktop applications was not a resource-effective way to go. You must create multiple copies of the same software for every OS and hire teams to maintain and upgrade them.
You must install and update them manually, making it harder to use them across devices.
We needed a platform that allows us to build a product once and deliver it to all customers regardless of their platform of choice. The browser fits this description perfectly.
We can build an application once, and it will be available on every machine with a network connection. Updates are a matter of refreshing the page, and the team required to maintain it will be significantly smaller.
But there’s one problem.
We didn’t know how to build web applications.
...
In other words, the JS toolchain is deeply fragmented. The thing I dread the most is having to set up an entire project from scratch and piece up the configuration puzzle so it can work.
The simplest example of our perils as JavaScript engineers is that eslint and prettier, two tools used together all the time, require additional config, so they’re not in conflict with each other.
But tooling fragmentation can go much deeper.
...