Pure vs Semantic UI: What are the differences?
What is Pure? A set of small, responsive CSS modules that you can use in every web project. Pure is meant to be a starting point for every website or web app. We take care of all the CSS work that every site needs, without making it look cookie-cutter.
What is Semantic UI? A UI Component library implemented using a set of specifications designed around natural language. Semantic empowers designers and developers by creating a shared vocabulary for UI.
Pure and Semantic UI belong to "Front-End Frameworks" category of the tech stack.
Some of the features offered by Pure are:
- A responsive grid that can be customized to your needs
- A solid base built on Normalize.css to fix cross-browser compatibility issues
- Consistently styled buttons that work with and
On the other hand, Semantic UI provides the following key features:
- Build Responsive Layouts Easier
- Self Explanatory
- Tag ambivalent
"Lightweight" is the primary reason why developers consider Pure over the competitors, whereas "Easy to use and looks elegant" was stated as the key factor in picking Semantic UI.
Pure and Semantic UI are both open source tools. It seems that Semantic UI with 45.7K GitHub stars and 4.83K forks on GitHub has more adoption than Pure with 20K GitHub stars and 2.06K GitHub forks.
What is Pure?
What is Semantic UI?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Pure?
What are the cons of using Semantic UI?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Pure?
Sign up to get full access to all the tool integrationsMake informed product decisions
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.