Ranked in these QuestionsQuestion Ranking
Pro Great-looking demo
Pro Device agnostic
Since Materialize follows Google's guidelines for Material design, which in theory is device agnostic, Materialize itself is device agnostic too. It's designed to look good on every device.
Pro Large selection of components
CSS components: Badges, buttons, cards, collections, footer, forms, icons, navbar, pagination, preloader.
Mobile-specific: slide-out drawer menu, toasts.
Pro Mobile navigation
Pro Nice showcase of sites built with Materialize
While the default style is not bad at all, Materialize also gives developers the ability to customize it and fit their own style, while still keeping in line with the Material Design philosophy.
Along with the CSS files, designers can also download the SASS files which can be edited and compiled.
Pro 12-Column Grid System
Pro Included icon font
Pro Meteor.js integration by developers
Material design is very opinionated on how design elements should behave and look. The basics of which revolve around certain visual elements (physics, space, momentum and light) which are used to create specific UX elements.
This is very helpful because it creates a consistent feel without making every design look the same. This can be seen in Materialize too, where each element may be customized but still it keeps the consistent look of the material design.
Pro Completely free and open source
Most UI frameworks seems to be really limited or cost money. Fit.UI is actually quite comprehensive and licensed under LGPL which means you can use it for any kind of project - commercial, personal, or open source.
Pro Full intellisense for JS and TypeScript in Visual Studio Code
You never have to look look up the names of functions - Visual Studio code just lists all the possible functions available on a given Fit.UI object.
Pro NPM package available
It can easily be installed through npm:
npm install fit-ui.
Pro Enhances productivity
You can create a fairly complex app in little time from scratch using Fit.UI.
Con Not maintained anymore
Con Large / heavy
267 kilobytes, minified, for the CSS and JS.
No longer supported by their maintainers.
Con Not as much third-party resources available
Since it's not as popular as other libraries there are not as many third-party resources like plugins or tutorials available.