4 ms·
You can still use vanilla-OO React. Do you complain when other frameworks add new features without breaking backwards compatibility?
by Hasu 2y ago
You can still use vanilla-OO React.
Do you complain when other frameworks add new features without breaking backwards compatibility?
- trgn 2y agoI certainly did complain! And I'm sure I'll do it again if the new features aimed to supplant the old ones are worse. If you search anything about React now, 90% of the docs are hook-based. Beginners of React in 2025 will be guided to use a default pattern which has worse runtime footprint and adds a whole suite of new tool-specific coding guidelines ("rules of hook"). After years with it, I struggle to see what it has added in terms of building front-end SPas, yet the pattern is now the default for all using React.
- CharlieDigital 2y ago> You can still use vanilla-OO React What we want is signals-based React because it would singularly fix the issue that the compiler is solving for and remove the need to even have `useMemo` and `useCallback`, improve performance, and remove a huge footgun. Because it has such a huge marketshare, a fix like this would have tremendous positive effects in web dev. We are all "forced" to use React so it would do all of us a great service if the team would just backstep and say "Oops, we made a design mistake here!". Instead, they spent almost 3 years building the compiler to sprinkle in memoization primitives because enough devs cannot get it right.