3 ms·
That seems to be a common attitude with front-end devs these days, to the detriment of web users. The performance impact of React, Angular, any other heavy fro
by OkGoDoIt 7y ago
That seems to be a common attitude with front-end devs these days, to the detriment of web users. The performance impact of React, Angular, any other heavy frontend SPA framework is immense. Plus the extra weight required to get back to feature-parity with frameworkless (url rewriting, scroll reworking, etc). There are some complicated web apps like GMail where an SPA makes sense (although it's still super slow and heavy), but I've been on so many corporate teams where there's a big push to move a traditional site to React/Angualar/etc and it's never worth it. Development productivity is not worth sacrificing usability, and often developer productivity doesn't actually improve anyway. But I always seem to be fighting an uphill battle in this regard. I'm in the process of realigning my career away from full-stack dev nowadays because the state of frontend dev is so horrendous, I want no part of it anymore.
- ng12 7y agoI honestly don't know what you're talking about. What performance impact? As I mentioned above I've never encountered a major performance problem in a React application, even on very old browsers. Regarding your other concerns I suspect you and I work on very different types of projects.
- viklove 7y agoCan you share some React-based webapps that have poor performance?