Componentization on React (and other frameworks like it) is just generally an antipattern #react #reactjs #programming #frontend
University and bootcamp instructors may dock marks off for improper componentization, but these people are really behind on what people in the Industry do.
Don't listen to them.
If you want to componentize, because it is easier for you, then do it.
If it doesn't bother you to *not* componentize, then don't bother #reactjs #react #frontend
@manlycoffee what is it that your implying that “people in the industry” do in favor or component driven development? From what I’ve observed component driven development is the dominant front end paradigm for good reason. increased productivity, scalability, maintainability, UX, DX… pretty much all the things are better for it.
@ryanlegler I'm not denying that component-driven development is the dominant paradigm.
Just that with the advent of Tailwind and CSS-in-JS, I'm increasingly beginning to see people reduce the amount of componentization in their code.
By componentization, I'm also including the act of defining custom CSS classes.
People are doing this less and less.
This approach is especially useful if we need to apply a style to only a single part of an entire application. No point having that be its own component or even its own CSS class.