|
|
|
|
|
|
by bombtrack
2741 days ago
|
|
|
I don't think equating 1 route = 1 component makes much sense. A route could be as simple as `/user/123` which shows an avatar and a name, or it could be `/billing` which has many sub-routes and complex features behind it. To just jump to an example of an extreme case, Facebook has stated several times they have tens of thousands of components [0]. Now, I assume lots of folks on HN work for private companies that build a wide swath of applications ranging from trivial to massively complicated. Why is it outlandish to think people wouldn't have many components in an app? [0]: https://www.reddit.com/r/reactjs/comments/6al7h2/facebook_ha... |
|
|