Need advice about which tool to choose?Ask the StackShare community!
Bourbon vs Sass: What are the differences?
Developers describe Bourbon as "A lightweight mixin library for Sass". Bourbon is a library of pure sass mixins that are designed to be simple and easy to use. No configuration required. The mixins aim to be as vanilla as possible, meaning they should be as close to the original CSS syntax as possible. On the other hand, Sass is detailed as "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.
Bourbon and Sass belong to "CSS Pre-processors / Extensions" category of the tech stack.
"Simple mixins" is the primary reason why developers consider Bourbon over the competitors, whereas "Variables" was stated as the key factor in picking Sass.
Bourbon and Sass are both open source tools. It seems that Sass with 12K GitHub stars and 1.93K forks on GitHub has more adoption than Bourbon with 8.84K GitHub stars and 916 GitHub forks.
According to the StackShare community, Sass has a broader approval, being mentioned in 2082 company stacks & 1446 developers stacks; compared to Bourbon, which is listed in 25 company stacks and 12 developer stacks.
What is Bourbon?
What is Sass?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Bourbon?
Why do developers choose Sass?
- Variables599
- Mixins583
- Nested rules465
- Maintainable414
- Functions295
- Open source139
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Bourbon?
What are the cons of using Sass?
What companies use Bourbon?
What companies use Sass?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
ReactQL
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.
Rent the RunwayWe 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
SassIt 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.
SassSass 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.
SassWhen 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.
SassSass 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.
SassCSS 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.
BourbonUsing Bourbon Neat for building a grid. It's easy to implement and is added to the CSS rather than the html which keeps similar modules looking the same.
Bourbon[Free] We use this free Sass framework on just about any project that we work on.
BourbonReplaced Foundation grid system with Bourbon Neat.