| ▲ | r0m4n0 5 hours ago |
| I have never been able to pick the framework and libraries for my day job. I’m almost always working on something someone started years prior or bound to an organization that has strict choices. Personally I wouldn’t pick react :) React wins because it has become a default choice and folks like what’s comfortable to their preferences |
|
| ▲ | pibaker an hour ago | parent | next [-] |
| I mean, that means someone at your work liked React enough to choose it over the alternatives. I see a lot of personal projects, solo founder applications etc running made in React. I respect your opinion but other people definitely do choose it when they have fully control of what they use. |
| |
| ▲ | TonyStr an hour ago | parent | next [-] | | Most decision-makers make decisions based on what they already know. Most of my colleagues only know React, because they've only been exposed to React. Why do you think Java dominates the market still? React solved a huge problem when it was new, and it still solves that problem fine (change detection - the reactivity model). There are better alternatives available now (Vue - signals), but the difference isn't big enough to create a new monoculture. Sure there are peripheral concerns like how mature the ecosystem is or the particular ergonomics of a framework, but these are mostly fluff. | |
| ▲ | janalsncm an hour ago | parent | prev [-] | | That doesn’t mean they like it now, and more importantly it doesn’t mean it was actually the best choice at the time. I used to be on a team that used Mongo for a relational database because Mongo was trendy at one time. So all joins had to be done in the application layer. |
|
|
| ▲ | curtisblaine 3 hours ago | parent | prev [-] |
| React wins because it has a predictable interface that has become industry standard. Industry standard saves money. Not everything must be creative. |
| |
