ngx-bootstrap VS primeng

The problem is that the UI component framework used in the course hasn't been updated yet for version 16 - see https://github.com/valor-software/ngx-bootstrap/issues/6579

with ngx-bootstrap I mean valor-software-ngx-bootstrap.

artillery quick --count 15 -n 30 https://valor-software.com/ngx-bootstrap/ With this command, the test will run 15 virtual users with each of them making 30 HTTP GET requests to the URL address that you specified.‌

Github Stars: 5100+

The NGX Bootstrap library has about 5.3K stars on GitHub. Here you can find basic components that implement the capabilities of the Bootstrap template written specially for Angular. It is suitable for developing desktop and mobile applications and is designed with extensibility and adaptability in mind. One of the features of this library is a variety of element forms. Among the element forms that could be added to your application, accordion with custom HTML, various forms of carousels, pager pagination, and different ratings deserve special mention. Custom HTML component of NGX Bootstrap library (source: https://valor-software.com/ngx-bootstrap/) Basic carousel component of NGX Bootstrap library (source: https://valor-software.com/ngx-bootstrap/)

Github Stars: 5100+ Weekly npm downloads: 11,000+ Latest update: 2.0.1

PrimeNg GitHub

> It’s important to be aware of what you are getting if you go with React, and what you are getting is a far cry from what a framework would offer, with all the corresponding pros and cons.

Would you like to elaborate on that?

In my experience, with something as great, size/ecosystem-wise as React, there will almost always be at least one "mainstream" package for whatever you might want to do with it, that integrates pretty well. Where a lot of things might come out of the box with a framework, with a library I often find myself just needing to install the "right" package, and from there it's pretty much the same.

For example, using https://angular.io/guide/i18n-overview or installing and using https://react.i18next.com/

Or something like https://angular.io/guide/form-validation out of the box, vs installing and using https://formik.org/

Or perhaps https://angular.io/guide/router vs https://reactrouter.com/en/main

Even adding something that's not there out of the box is pretty much the same, like https://primeng.org/ or https://primereact.org/

React will typically have more fragmentation and therefore also choice, but I don't see those two experiences as that different. Updates and version management/supply chain will inevitably be more of a mess with the library, admittedly.

Now, projects like Next https://nextjs.org/ exist and add what some might regard as the missing pieces and work well if you want something opinionated and with lots of features out of the box, but a lot of those features (like SSR) are actually pretty advanced and not always even necessary.

PrimeNG (MIT license)

PrimeNg Release Notes

PrimeNG: Something nice about this collection is how you choose the base theme. You are presented with choosing design options that are taken from other popular design frameworks such as Material Design, Bootstrap, Soho, Fluent, Nano, and more. This is done with a visual editor, which is part of the theming options. PrimeNG also has a Figma UI kit, ready-made templates, and a SASS API.

PrimeNG is released under the MIT License https://github.com/primefaces/primeng/blob/master/LICENSE.md

We use PrimeNG which MIT licensed. It's great.

After months of hard work, we're excited to share the new major update on PrimeNG that mostly focuses on the documentation.