3 ms·
Just FYI a couple of heavy hitters you might wanna add to the list: - Adobe spectrum: https://spectrum.adobe.com/ https://spectrum.adobe.com/ - Radix UI: http
by autoconfig 4y ago
Just FYI a couple of heavy hitters you might wanna add to the list:
- Adobe spectrum: https://spectrum.adobe.com/ https://spectrum.adobe.com/
- Radix UI: https://www.radix-ui.com/ https://www.radix-ui.com/
- Tailwind UI: https://tailwindui.com/ https://tailwindui.com/
- Reach UI: https://reach.tech/ https://reach.tech/
- eddieh 4y agoAdobe has http://topcoat.io http://topcoat.io too. How many companies have multiple component libraries/frameworks? Seems like a lot of wasted time and resources.
- q7xvh97o2pDhNrh 4y agoEvery company has a frontend team, and all of those frontend folks want to get promoted. Building an in-house component library is a straightforward card to play. It's basically the natural outcome of reasonable people responding in reasonable ways to seemingly-reasonable incentive structures. (I do agree there's probably a more efficient way, but I think it might also be one of those slippery-slope situations where there's a lot of gravity pulling sufficiently-large teams to eventually have their own component library. In other words: Suppose they start off with the best of intentions and repurpose an existing library. Then come the inevitable months of customization, forking, racing to integrate upstream updates, etc. Finally, someone pipes up and says, "Hey, why don't we build our own so we can control our own destiny?" Stakeholders get excited, and then it's off to the races.)
- manigandham 4y agoThanks, added to the list