I wouldn't necessarily be concerned about a project using components from other open-source projects. The whole idea of open source is to share and reuse. And in this case it looks like the react-component repositories are specifically meant to serve as the foundation for Ant Design:
Thanks for reply. I know that react-component becomes foundation of Antd. But I want to compare it with similar UI component toolkits such as Bootstrap, Material-UI, Materialize and Foundation by Zurb. Bootstrap team created the main or the core of their components by themselves. They do take some of 3rd party libraries such as popper.js to support dropdown, popover and tooltips components.
Whereas Antd, a lot of the UI components (rc-) are taken from react-component repo. I guess, perhaps because some of developers that maintain react-component project are also team member or have relation to Antd team. Looking at who created the original of rc-menu, I can understand why.
Alright, this is actually not really a problem for me, as I am impressed with some its components, especially menu with submenu, select and layout.
Btw, why do you pick Reach-Router instead of React-Router which is more popular ?
I prefer the simplicity of Reach Router (you can see an overview of the differences here). But the good news is that React Router will soon be adopting the Reach Router API, as discussed here. So at this point they're largely the same and migrating from one to the other shouldn't take long.
Thanks for reply. I got it. I have read both links you gave. Actually, I only use React-Router for its basic usage, haven't dived deeper, because there are other things that need more attention from me, being a full-stack developer.
As explained in the link about the feature of React-Router and Reach Router, I think I can wait for the new release of React-Router which will adopt the goods from Reach Router as well as keeping or enhancing the goods from itself.
While waiting for the new release of React Router, I agree that Reach Router looks simple that it is worth for a try.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I wouldn't necessarily be concerned about a project using components from other open-source projects. The whole idea of open source is to share and reuse. And in this case it looks like the react-component repositories are specifically meant to serve as the foundation for Ant Design:
Thanks for reply. I know that react-component becomes foundation of Antd. But I want to compare it with similar UI component toolkits such as Bootstrap, Material-UI, Materialize and Foundation by Zurb. Bootstrap team created the main or the core of their components by themselves. They do take some of 3rd party libraries such as popper.js to support dropdown, popover and tooltips components.
Whereas Antd, a lot of the UI components (rc-) are taken from react-component repo. I guess, perhaps because some of developers that maintain react-component project are also team member or have relation to Antd team. Looking at who created the original of rc-menu, I can understand why.
Alright, this is actually not really a problem for me, as I am impressed with some its components, especially menu with submenu, select and layout.
Btw, why do you pick Reach-Router instead of React-Router which is more popular ?
I prefer the simplicity of Reach Router (you can see an overview of the differences here). But the good news is that React Router will soon be adopting the Reach Router API, as discussed here. So at this point they're largely the same and migrating from one to the other shouldn't take long.
Thanks for reply. I got it. I have read both links you gave. Actually, I only use React-Router for its basic usage, haven't dived deeper, because there are other things that need more attention from me, being a full-stack developer.
As explained in the link about the feature of React-Router and Reach Router, I think I can wait for the new release of React-Router which will adopt the goods from Reach Router as well as keeping or enhancing the goods from itself.
While waiting for the new release of React Router, I agree that Reach Router looks simple that it is worth for a try.