Repository navigation
After Primeng 21 - what now? MIT, true open source, sovereignty #234
Replies: 2 comments 2 replies
|
Happy to share some thoughts. This is definitely something worth taking some time to think about because the migration cost could be significant. I never used Open Prime, so I'm not sure how reliable the community is. That said, since it's based on PrimeNG, the transition would probably require much less work. On the other hand, I would recommend sticking with Angular Material. I don't think it's going to disappear, and it should remain open source. The downside is that the migration will probably be more difficult. One advantage is that AI coding tools will likely adapt better to Angular Material because it's the official Angular UI library. I also heard that Angular is moving to one major release per year, in sync with Angular Material. If that's true, it could be good news if you decide to migrate to Angular Material, since keeping everything up to date should become easier. |
|
For a self-hosted privacy product I would not pick another large kit whose vendor can flip the license again. Lowest-risk long term is Angular CDK plus a small set of primitives you own (dialog, menu, table) — more work, but the governance stays yours. open-prime is the cheap migration if it actually stays a community fork; I'd wait for a few months of commit history and an explicit license guarantee before betting the UI on it. Spartan is nicer DX (shadcn-shaped) but it's still someone else's design system to absorb. Material is stable and MIT, and the migration cost from PrimeNG is the painful part either way. |
Uh oh!
There was an error while loading. Please reload this page.
Happy to gather same suggestions:
Problem: We use PrimeNG as UI component library, however they moved away from open-source
Goals:
Options:
All reactions