Bourbon vs PostCSS: What are the differences?
What is Bourbon? 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.
What is PostCSS? Transform CSS with JS plugins. 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.
Bourbon and PostCSS belong to "CSS Pre-processors / Extensions" category of the tech stack.
"Simple mixins" is the top reason why over 13 developers like Bourbon, while over 17 developers mention "The "babel" of CSS" as the leading cause for choosing PostCSS.
Bourbon and PostCSS are both open source tools. It seems that PostCSS with 21.1K GitHub stars and 1.15K forks on GitHub has more adoption than Bourbon with 8.86K GitHub stars and 916 GitHub forks.
According to the StackShare community, PostCSS has a broader approval, being mentioned in 63 company stacks & 47 developers stacks; compared to Bourbon, which is listed in 25 company stacks and 12 developer stacks.
What is Bourbon?
What is PostCSS?
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 Bourbon?
What are the cons of using PostCSS?
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 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 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
PostCSS essentially allows you to set up your own CSS preprocessor with the features that matter to you. It has a modular plugin-based architecture, which means that if someone comes up with a useful new feature, you can easily add it to your stack as a PostCSS plugin. PreCSS and PostCSS-cssnext are some of my go-to plugins.
PostCSS handles compiling node-based CSS libraries, including BassCSS (the whole site is only ~85 lines of custom CSS). It also does auto-vendor-prefixing and support for CSS variables.
Using 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.
We wrote a lot of flexbox and css that needed prefixing. PostCSS + Webpack was the best option here.
[Free] We use this free Sass framework on just about any project that we work on.