Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Semantic UI vs PostCSS, the Slant community recommends Semantic UI for most people. In the question“What are the best minimal CSS frameworks?” Semantic UI is ranked 7th while PostCSS is ranked 12th. 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.
Question 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 Fast
PostCSS is 3-30 times faster than Sass (including libsass), Less, and Stylus
Pro Flexible
PostCSS allows you to opt-in to the features you need with plugins. This allows you to set it up to behave exactly like Sass, with nesting, mixing, extends, and more. On the other hand, it allows you to use plugins by themselves for things like auto-prefixing, minification, and more. You can even set up your own custom "stack" of plugins to do exactly what you like.
Pro Doesn't force designers to learn a new syntax
Rather than learn a different syntax, PostCSS allows you to write in pure CSS.
Pro JavaScript-based out of the box
Since it's basically CSS extended through JavaScript it works in the browser directly without the need to compile it beforehand.
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 Harder to install and keep working
The immense flexibility of PostCSS plus its current rapid evolution makes it harder to install, configure and keep running than the more monolithic and mature preprocessors.
Con Outdatet, plugins are often based on different postcss versions and don't work together properly
Con Some plugins need to run in a certain order
Some plugins can only work if initialized after some other plugins. For example, transforming and applying CSS variables needs to run before running a plugin which uses these variables inside conditional transformations.
