Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

When a business decides to pick a tech, they look at following:

1. Longevity

2. Market share

3. Developer supply

4. Third party support. (Ecosystem)

5. Technically mature and advanced

Among those criteria react excels at first four. And is good enough for the fifth.

So, most business will pick react. Depending on the local environment, some may pick angular for those same reason.

All newer, better technologies will be evaluated afterwards and only if react and angular prove to be too troublesome for the business's current needs.

This is why "react new" is not a thing. This sentiment is echoed almost weekly basis. Recent threads were under title "React is holding me hostage"



I don't understand how any of that is related to why "react new" is not a thing.


Then let me iterate it more clearly. The reason "react new" is not a thing because from business perspective "react" is superior to "react new".

Hence newer projects are likely to pick react instead of solid/svelte


For posterity’s sake, they weren’t suggesting a new React, they were describing a missing official way to create a new app at the command line like “react new my-todo-app”




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: