When comparing Semantic UI vs WebUI, the Slant community recommends Semantic UI for most people. In the question“What is the best CSS framework?” Semantic UI is ranked 6th while WebUI is ranked 16th.
Ranked in these QuestionsQuestion Ranking
Pro The elements offer a huge amount of customization, far beyond a framework like bootstrap.
Pro Load only the components you need
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 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
Pro Scalable CSS transform and SVG shapes
WebUI includes scalable CSS transform shapes and scalable clip-path shapes.
Pro Supports build customisation
Build customisation allows components that aren't required to be excluded using SASS includes and grunt tasks.
Pro Full support for flexbox
WebUI includes a full range of flexbox classes, including breakpoint specific classes based on REM units.
Pro Multiple grid systems out of the box
WebUI includes a flexbox, a table, and standard grid systems. These grid types can be used in combination and together.
Pro Generic design
Every component is built to be generic and interchangeable. For example, there are no restrictions on where grids, containers, menu buttons, or dropdowns can be used.
Pro Powerful tooltip system
The tooltip system includes viewport boundary collision detection, auto positioning and auto sizing for small viewport areas, configurable boundary margins, and many behavioral settings, such as focus, hover, static, nohide.
Con Very 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.
Contains a lot of UI inaccuracies, like wrong positioning, cannot mix classes, etc.
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".