4 ms·
> You're completely missing the reason that all these "hopelessly over-engineered" frameworks were created They were created in a very different time, to solve
by lelanthran 2y ago
> You're completely missing the reason that all these "hopelessly over-engineered" frameworks were created
They were created in a very different time, to solve very different problems in a very different runtime environment.
Today's browser environment does not have many of the problems these frameworks were created to solve, and the clear majority of usage in the wild solves the existing problems in a way that locks you in to the framework anyway.
When I say over-engineered I don't mean that they were not necessary in the past, I'm saying that right now, in 2025, a lot of what you get from these frameworks is disproportionate to the cognitive burden they bring.
I agree that they solve problems, I'm just saying that perhaps it is time to consider that the point of diminishing returns has passed.
- edanm 2y agoYeah I think we agree; historically necessary, less clear if necessary now. My feeling as a not-very-in-the-loop person is that React is still the correct default choice nowadays, but it's complicated because of how entrenched it is - that is its own kind of reason to choose a solution.