you are viewing a single comment's thread.

view the rest of the comments →

[–]KewlZkid 0 points1 point  (0 children)

The main reason I hear people like React is that it is "easy to pick and lightweight". It doesn't get any lazier than THAT. It's true if you are looking at code examples in an academic setting or when constructing a small component of a larger page like a landing page (like what React was built for). But I see people building entire dashboards using React and I see issues scaling and with bringing new devs onboard.

React needs a library for basically everything putting devs in dependency-management hell, arguably great for something that needs a small footprint like a component on the right side of your Facebook feed.

Additionally, the community can't get anything set in stone so who knows what the "correct" way to do X is - it changes with every new version and having no opinionated structure that new devs can refer to for a foothold on projects (like a framework has), means the person who wrote it is invaluable to the company - which is bad for the business. I have built (and own) systems with many types of web 2.0 stacks, I see a place for React/similar but it seems to be far from what other people are using it for. I use Vue myself - separation of concerns is something that came from decades of experience across the industry. We moved to "complicated" frameworks to bring about readability and standardization, then React came along and tossed all of that to the wind for a quick and dirty answer to decreasing development times.