Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Sass
Sass

11.4K
7.6K
+ 1
3K
Semantic UI
Semantic UI

611
610
+ 1
577
Add tool

Sass vs Semantic UI: What are the differences?

Sass: Syntactically Awesome Style Sheets. Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin; 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.

Sass and Semantic UI are primarily classified as "CSS Pre-processors / Extensions" and "Front-End Frameworks" tools respectively.

"Variables", "Mixins" and "Nested rules" are the key factors why developers consider Sass; whereas "Easy to use and looks elegant", "Variety of components" and "Themes" are the primary reasons why Semantic UI is favored.

Sass and Semantic UI are both open source tools. It seems that Semantic UI with 45.9K GitHub stars and 4.84K forks on GitHub has more adoption than Sass with 12K GitHub stars and 1.93K GitHub forks.

According to the StackShare community, Sass has a broader approval, being mentioned in 2101 company stacks & 1485 developers stacks; compared to Semantic UI, which is listed in 77 company stacks and 55 developer stacks.

What is Sass?

Sass is an extension of CSS3, adding nested rules, variables, mixins, selector inheritance, and more. It's translated to well-formatted, standard CSS using the command line tool or a web-framework plugin.

What is Semantic UI?

Semantic empowers designers and developers by creating a shared vocabulary for UI.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Sass?
Why do developers choose Semantic UI?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use Sass?
      What companies use Semantic UI?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Sass?
      What tools integrate with Semantic UI?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Sass and Semantic UI?
      Stylus
      Stylus is a revolutionary new language, providing an efficient, dynamic, and expressive way to generate CSS. Supporting both an indented syntax and regular CSS style.
      styled-components
      Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 馃拝
      PostCSS
      PostCSS is a tool for transforming CSS with JS plugins. These plugins can support variables and mixins, transpile future CSS syntax, inline images, and more.
      Bootstrap
      Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.
      Less
      Less is a CSS pre-processor, meaning that it extends the CSS language, adding features that allow variables, mixins, functions and many other techniques that allow you to make CSS that is more maintainable, themable and extendable.
      See all alternatives
      Decisions about Sass and Semantic UI
      Koa
      Koa
      React Router
      React Router
      Foundation
      Foundation
      Semantic UI
      Semantic UI
      Bootstrap
      Bootstrap
      PostCSS
      PostCSS
      Less
      Less
      Sass
      Sass
      styled-components
      styled-components
      React Helmet
      React Helmet
      Webpack
      Webpack
      TypeScript
      TypeScript
      JavaScript
      JavaScript
      Apollo
      Apollo
      GraphQL
      GraphQL
      React
      React
      #JSX
      #React.
      #Css
      #StyledComponents.
      #Async
      #HTML
      #GraphQL
      #Apollo

      ReactQL is a React + GraphQL front-end starter kit. #JSX is a natural way to think about building UI, and it renders to pure #HTML in the browser and on the server, making it trivial to build server-rendered Single Page Apps. GraphQL via Apollo was chosen for the data layer; #GraphQL makes it simple to request just the data your app needs, and #Apollo takes care of communicating with your API (written in any language; doesn't have to be JavaScript!), caching, and rendering to #React.

      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.

      styled-components, Sass, Less and PostCSS were added to give developers a choice of whether to build styles purely in React / JavaScript, or whether to defer to a #css #preprocessor. This is especially useful for interop with UI frameworks like Bootstrap, Semantic UI, Foundation, etc - ReactQL lets you mix and match #css and renders to both a static .css file during bundling as well as generates per-page <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.

      See more
      Hampton Catlin
      Hampton Catlin
      VP of Engineering at Rent The Runway | 4 upvotes 58.8K views
      atRent the RunwayRent the Runway
      styled-components
      styled-components
      PostCSS
      PostCSS
      Sass
      Sass

      We use Sass because I invented it! No, that's not a joke at all! Well, let me explain. So, we used Sass before I started at Rent the Runway because it's the de-facto industry standard for pre-compiled and pre-processed CSS. We do also use PostCSS for stuff like vendor prefixing and various transformations, but Sass (specifically SCSS) is the main developer-focused language for describing our styling. Some internal apps use styled-components and @Aphrodite, but our main website is allllll Sassy. Oh, but the non-joking part is the inventing part. /shrug

      See more
      Interest over time
      Reviews of Sass and Semantic UI
      No reviews found
      How developers use Sass and Semantic UI
      Avatar of Kevin Ard
      Kevin Ard uses SassSass

      It was a little awkward building BS3 with LESS, and the rest of the site with SCSS, but it works. SCSS made building the UI elements (ink/flip buttons, img navs, etc) a breeze. It also drives the mobile menu open/close transitions - that would have been much too much with vanilla css.

      Avatar of Climate CoLab
      Climate CoLab uses SassSass

      Sass helps us write better stylesheets. One major improvement over CSS that we use a lot is variables - it allows for much easier theming to quickly change brand colors for new instances of the xCoLab.

      Avatar of Ujjwal Bhujel
      Ujjwal Bhujel uses SassSass

      When you realise that countless lines of CSS codes could be made countable. And off course, a wonderful and cool way to use the logic behind variables and nesting. Simply love it.

      Avatar of Scrayos UG (haftungsbeschr盲nkt)
      Scrayos UG (haftungsbeschr盲nkt) uses SassSass

      Sass is used as a part of Woltlab Suite Core, which offers to submit/configure own styles via the injection of own Sass-CSS. So we exclusively rely on Sass for our CSS needs.

      Avatar of Refractal
      Refractal uses SassSass

      CSS is a mess. There, we said it. Sass, on the other hand takes CSS and makes it pretty, easy to work with and has stuff like variables which make things seriously awesome.

      Avatar of osu! Ripple
      osu! Ripple uses Semantic UISemantic UI

      We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.

      Avatar of Ralic Lo
      Ralic Lo uses Semantic UISemantic UI

      Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.

      Avatar of Giftstarter
      Giftstarter uses Semantic UISemantic UI

      We haven't yet, but we would like to integrate into our Web App.

      Avatar of Eliana Abraham
      Eliana Abraham uses Semantic UISemantic UI

      It's pretty. Used it once for MDST.

      Avatar of Wellzesta
      Wellzesta uses Semantic UISemantic UI

      Grid, widgets, theming.

      How much does Sass cost?
      How much does Semantic UI cost?
      Pricing unavailable
      Pricing unavailable
      News about Semantic UI
      More news