3 ms·

I can do better. Get rid of React and the other client-side libraries that reimplement the DOM interface in Javascript except slower and more brittle.

• steve_adams_86 6y ago
  For what it’s worth, I’ve been profiling front end applications for over a decade, and the only time application bundle size was a real problem was very rare. On the other hand, people writing terrible code usually was the problem, and it would have happened with or without react. I think we’d see faster websites more often if developers had worse computers, or they invested more time in testing in resource constrained environments. I really don’t think react (or similar) is the core problem.
  • RedShift1 6y ago
    This, absolutely. Every developer should get like a Pentium 3 500 MHz and 512 MB of RAM to make their software work.
  • otabdeveloper4 6y ago
    Who said anything about bundle size? There's already a "browser platform framework", it's standard, built into your browser and very fast. Trying to re-implement the browser inside the browser using Javascript is a recipe for disaster. (Indeed: witness the "modern" web.) I get that something more enterprisey-feeling with more knobs for programming in the large is more agreeable to the assembly-line programmer in large IT shops, but if you want your browser apps to act nice you'll have to suck it up and program natively without the overhead of a framework.