When comparing Semantic UI vs Materialize, the Slant community recommends Semantic UI for most people. In the question“What is the best CSS framework?” Semantic UI is ranked 7th while Materialize is ranked 13th. The most important reason people chose Semantic UI is:
Uses semantic class names for its styling, making it easier to grasp and understand even for beginners looking to jump right in.
Ranked in these QuestionsQuestion Ranking
Pros
Pro It's semantic
Uses semantic class names for its styling, making it easier to grasp and understand even for beginners looking to jump right in.
Pro Load only the components you need
The whole Semantic-UI package is well organized, with every component neatly set up with it's own stylesheet and JavaScript file. This way you can load only the components you need for each page, minimizing the load time and file size.
Pro The elements offer a huge amount of customization, far beyond a framework like bootstrap
Pro Beautifully designed
Semantic UI has a futuristic and beautiful design. Many will satisfied with the design, especially when Semantic UI is used as a CSS framework.
Pro It'll have almost any UI component/element you may think of for your project
It includes tons of UI components that you may need for almost any type of project you may work on; And of course, you can always only pick what you need.
Pro Well documented
The documentation is easy to use, well written and has lots of examples each with their source codes.
Pro Easy to use
Just start code from the beginning of the journey, from first page of documentation.
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.
JavaScript components: Collapsible, Dialogs, Dropdown, Media, Modals, Parallax, Pushpin, ScrollFire, Scrollspy, SideNav, Tabs, Transitions, Waves.
Mobile-specific: slide-out drawer menu, toasts.
Pro Responsive
Pro Mobile navigation
Pro Nice showcase of sites built with Materialize
Pro Customizable
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
Pro Opinionated
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.
Cons
Con Large file size
Packages are much bigger when comparing to Twitter Bootstrap or Zurb Foundation. Semantic UI is really extremely large and it would be better to use specific modules and components, rather than the whole thing.
Con Not maintained anymore
Use Fomantic-UI instead.
Con Buggy
Contains a lot of UI inaccuracies, like wrong positioning, cannot mix classes, etc.
Con Not for beginner developer/unfamiliar with Javascript
Many features in Semantic UI uses Javascript customization such as for Modal. This is unlike Bootstrap that can add Modal just with customizing the HTML attributes. Developers who plan to using Semantic UI must be familiar with Javascript or JQuery to get the most out of it.
Con Small number of classes
Once you wanna do something that is not mentioned in the doc - prepare to spend an hour, then give up and implement a custom "workaround".
Con Refuses to use the flexbox model
Even though Materialize states that it only supports IE10+, which supports flexbox quite well, with prefixes, Materialize has refused to use Flexbox.
Con Not maintained anymore
Con Large / heavy
267 kilobytes, minified, for the CSS and JS.
Con Deprecated
No longer supported by their maintainers.