Everyone bought into "immutable" "no side-effects" "one way data flow" as this ultimate goal. But never thought what the tradeoff is.
And people get FOMO that they need to use a big thing that they couldn't write themselves.
Whereas if you throw out everything and just build only what you need, you get something infinitely more understandable and simpler, probably with some hand-rolled data-binding thing that you actually understand.
Most people don't understand how their frameworks are working under the hood. They are just relying on a nicely documented API...until anything goes wrong.
Trying to debug React for example is insane. And if you build your own custom store it re-renders 6 times when in dev. When I saw this...I knew React's days were numbered.
Yeah that’s the ultimate interview question from Facebook: “explain why this component calls render() 46 times” and the answer is “it doesn’t, it renders 47 times” and they have to bring in one of the core developers to stop all the head scratching.
Yeah, the last paragraph is the clincher. When it's going wrong, on fire, lagging out your browser, and you're adding console logs in effects to chase what is driving changes you've lost.
And people get FOMO that they need to use a big thing that they couldn't write themselves.
Whereas if you throw out everything and just build only what you need, you get something infinitely more understandable and simpler, probably with some hand-rolled data-binding thing that you actually understand.
Most people don't understand how their frameworks are working under the hood. They are just relying on a nicely documented API...until anything goes wrong.
Trying to debug React for example is insane. And if you build your own custom store it re-renders 6 times when in dev. When I saw this...I knew React's days were numbered.