Let's face it: In the FE, we are using the wrong technology in the wrong places. Frameworks with total DOM manipulation capabilities in React et al are not nee

Let's face it: In the FE, we are using the wrong technology in the wrong places. Frameworks with total DOM manipulation capabilities in React et al are not needed by almost the entirety of the web. They were built for the needs of services like social networks, stock/finance sites etc, which need to send constant updates to the remote client. Facebooks sends likes, shares, friend requests, messages, other numbers. Financial sites run tickers, statistics that are needed live. But the rest of the internet doesnt need those. The last thing you want to have in an ecommerce checkout page is to send any kind of update to the customer and confuse them. For that reason these pages are as simple as possible. We also keep any kind of conversion flow extremely simple for that reason. In fact, even in almost all the other applications outside of social networks, finance sites and the like, we keep everything extremely simple. But, we are running entire stacks, infra and a codebases built on such frameworks. Worse, we are sending all of the resulting blob to the device of the user to be processed and displayed. Nobody thinks about the users who are using average devices. Nobody even thinks about the users who have high spec devices but who are temporarily in a low-connection-bandwidth location. As a result, there is immense bloat both on the user side and organization side. Large fe epds are dealing with complex problems that stem from the complexity of the stack and the inappropriate frameworks that are used in inappropriate places. What's worse is that programmers must program. Boredom causes engineers to start solving problems dont merit solutions. This is further exacerbated by organizations pushing 'productivity' on their epds by counting prs, or features shipped, changes done etc. These two phenomena amplify each other and you end up with complexity on the front end that solves problems nobody cares about. Of course, engineers also have to do this to keep their jobs - keep busy or the organization wont like it. So the mainstream tech is digging its own complexity grave by its fad-driven, profit-maximizing, wrong-metric-optimizing behavior patterns. A product, user oriented perspective must come back to the frontend. Users must come first. Organizations must stop pushing for false 'productivity' that only helps to complicate everything. Correct tech/stack/framework must be used in the correct place.