Tampoco son malos, pero hay que saber para qué usarlos y cuándo usarlos. Una buena explicación y una buena solución la tenemos en Frameworks without the framework: why didn’t we think of this sooner?:
We’re shipping too much code to our users. Like a lot of front end developers, I’ve been in denial about that fact, thinking that it was fine to serve 100kb of JavaScript on page load – just use one less .jpg! – and that what really mattered was performance once your app was already interactive.
But I was wrong. 100kb of .js isn’t equivalent to 100kb of .jpg. It’s not just the network time that’ll kill your app’s startup performance, but the time spent parsing and evaluating your script, during which time the browser becomes completely unresponsive. On mobile, those milliseconds rack up very quickly.
If you’re not convinced that this is a problem, follow Alex Russell on Twitter. Alex hasn’t been making many friends in the framework community lately, but he’s not wrong. But the proposed alternative to using frameworks like Angular, React and Ember – Polymer – hasn’t yet gained traction in the front end world, and it’s certainly not for a lack of marketing.
Perhaps we need to rethink the whole thing.
