3 ms·
For me it's simply the bulkiness of it: - Babel transpilation aspect (time it takes to build, difficulties associated with ad-hoc debugging in production) - B
by cryptica 7y ago
For me it's simply the bulkiness of it:
- Babel transpilation aspect (time it takes to build, difficulties associated with ad-hoc debugging in production)
- Bundling/packaging aspect (same reasons as above; time it takes to build, debugging difficulties).
- Huge number of unnecessary dependencies which adds risks/vulnerabilities to projects.
You could argue that it's not React's fault, that it's more about the tooling but I think that it's React's stance on inlining HTML with JavaScript (JSX) which had paved the way for all that bulkiness. From the beginning the project wrongly assumed that:
- Transpilation and bundling doesn't have any costs.
- Dependencies (those needed to do all that fancy transpilation and essentially re-implementing the way the DOM works) don't carry any additional risk and are not a threat to application security, maintenance...
- apotheon 7y agoI personally loathe JSX, not because of JavaScript, but because it's a wholly unnecessary different syntax for JavaScript that just forces me to deal with SGML/XML problems in a new and more painful way, because it has crept into the application logic as well.