> The maintenance demands for using a heavy, evolving framework and a large graph of churning dependencies are tremendous and perpetual Counterpoint: If you re

> The maintenance demands for using a heavy, evolving framework and a large graph of churning dependencies are tremendous and perpetual Counterpoint: If you replace a frontend framework with backend components, as has been suggested a few times in this thread, those frameworks are even larger, and a lot of the basic functionality provided by React (such as components) is often provided by third-party packages. Sure, if you're using something like jQuery, then it's smaller and more stable, but the functionality is limited compared to both backend and frontend frameworks. Which of course might be 100% appropriate depending on the use case.