guildofgleks/ui vs. Angular Material vs. PrimeNG
Why Guild of Gleks UI?
Three libraries, three different bets. Here's the short version — every number below, plus the exact commands used to produce it, lives in the full technical comparison.
Where every byte counts
Bundle weight isn't an abstract concern — it's load time on a slow connection, it's your Lighthouse score, it's the size budget your team argues about every sprint. Measured from each library's real published npm package, minified and gzipped:
Guild of Gleks UIentire library — 30 components
Angular MaterialButton + Select + Dialog + Table only
PrimeNGButton + Select + Dialog + Table only
The entire library — all 30 components — is still smaller gzipped than just four components from either Material or PrimeNG.
What should you choose?
Guild of Gleks UI
Angular Material
PrimeNG
Theming
Plain CSS variables
Sass mixins / M3 tokens
JS preset system
Setup
npm install, import, done
+ @angular/cdk, theme mixins
+ 10 packages incl. CDK, a preset
Guild of Gleks UI
You want to ship fast, keep the bundle small, and restyle a component by setting a CSS variable — not by learning a theming API first.
Angular Material
You want Google's own design language and a decade of production hardening, and don't mind pulling in the CDK to get there.
PrimeNG
Your product needs something this library — or Material — simply doesn't have: rich data grids, charts, org charts, or one of dozens of specialized widgets.
Not trying to win every category
Guild of Gleks UI isn't trying to fix everything wrong with Angular UI libraries, replace Material or PrimeNG outright, or out-feature either one. It doesn't have a data grid, a chart, or an org chart, and it isn't pretending to.
Its actual claims are narrower and, hopefully, more honest: a lighter path to a finished UI than either alternative, and a bundle small enough that it barely registers in a size budget. Component breadth and ecosystem maturity are deliberate tradeoffs here, not oversights.
See exactly what's missing → How old a browser do you need?
All three currently track Angular's own "Baseline" browser policy for whichever Angular major they require — recent evergreen Chrome, Edge, Firefox and Safari, not a fixed old version. None of the three libraries layers its own separate browser floor on top of that.
If you're stuck supporting genuinely old hardware — Chrome 109-class machines are still common on corporate fleets — pinning an older release of Material or PrimeNG, built against an older Angular major, reaches back much further than this library can today. Guild of Gleks UI only has recent-Angular releases so far, so that fallback doesn't exist here yet.
