3 ms·

Things that aren't React's fault: 1. Everything you mentioned in your comment.

• anonymoushn 4y ago
  Implementing "responsive UI" using exclusively JavaScript and CSS-in-JS (rather than using CSS or not doing anything) was naughty and kludgey in 2010. The fact that it's now the "best practice" seems to have increased the rate at which forms delete themselves and the data users have typed in when the user makes the mistake of resizing the window (causing the user to briefly wonder whether computers have on the whole been worthwhile compared to the alternatives offered by mechanical printing presses, abacuses, papers, quills, and if one is feeling provocative, a typewriter, before repeating all the labor that they previously performed for their silicon master before it decided to unceremoniously discard it) Preventing the browser's "find" feature from searching the text on the page (causing the user to tear their hair out, bash their computer with a rock, borrow a wilderness survival book from the local library, drive to the countryside, abandon their vehicle at a rest stop, and renounce civilization once and for all) is a technique called List Virtualization and you can learn how to do it in React here: https://www.patterns.dev/posts/virtual-lists/ https://www.patterns.dev/posts/virtual-lists/. react-virtualized has over 1 million weekly downloads on npm. The benchmarks I was able to find comparing identical operations in different web frameworks look pretty bad for React as well.
  • tambourine_man 4y ago
    I like the way you roll, anonymoushn. Gave me a good laugh.