More importantly, instead of “which framework is better?” I wish more devs were asking “why do we need frameworks?” Did we miss teaching/learning fundamentals somewhere in the journey? Did we ever stop to learn or fully understand State driven design? Or did we just jump to a framework because some blog told us it was “fast”? Does your blog site really need a virtual DOM? Probably not. Is componetizing your site beneficial? Sure. But do you need React + Redux + React-router + a dozen other React libraries to achieve any of this? No. You most likely just skipped over the fundamental patterns of state driven design and understanding the observer pattern that most of these framework rely on. In fact, I’d say 90% of modern development can be described as “Resumé driven development”. If you’re a young dev and you look at job postings, they all say “must have experience in React/Angular” and that drives devs to one or the other without ever understanding the problems that these frameworks solve in the first place. My point is: if the only tool you ever learn to use is hammer, everything quickly becomes a nail. Stop trying to apply frameworks to everything and learn to be smart engineers who know that understanding when NOT to use a framework is just as important as choosing “which one is better”.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
More importantly, instead of “which framework is better?” I wish more devs were asking “why do we need frameworks?” Did we miss teaching/learning fundamentals somewhere in the journey? Did we ever stop to learn or fully understand State driven design? Or did we just jump to a framework because some blog told us it was “fast”? Does your blog site really need a virtual DOM? Probably not. Is componetizing your site beneficial? Sure. But do you need React + Redux + React-router + a dozen other React libraries to achieve any of this? No. You most likely just skipped over the fundamental patterns of state driven design and understanding the observer pattern that most of these framework rely on. In fact, I’d say 90% of modern development can be described as “Resumé driven development”. If you’re a young dev and you look at job postings, they all say “must have experience in React/Angular” and that drives devs to one or the other without ever understanding the problems that these frameworks solve in the first place. My point is: if the only tool you ever learn to use is hammer, everything quickly becomes a nail. Stop trying to apply frameworks to everything and learn to be smart engineers who know that understanding when NOT to use a framework is just as important as choosing “which one is better”.