|Hacker News, Reddit, Stack Overflow Stats|
|Description||The dynamic stylesheet language||A Stylesheet Authoring Environment that makes your website design simpler to implement and easier to maintain||Syntactically Awesome Style Sheets|
|Why people like using this service||
|Companies using this service|
Write less and achieve more
December 17, 2014 17:23
Absolutely fantastic, not only does it allow for modularity but it is armed with the most useful features like colour operations and nested styles to make you achive more by writing LESS.
love me some less. been less styling for around 3 years. makes working with bootstrap and responsive website a breeze. so much power in the language.
Extends our CSS by adding features that allow variables, mixins, functions etc to make CSS more maintainable and extendable.
Customise the UIkit Front-End Framework, because of that is used to create the application CSS. I prefer SASS but is equivalent.
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.
All of our CSS is first written in Sass (SCSS specifically). It is much easier to read and can keep styles DRYer with variables and functions.
only used this because people hated less, back then you still could not import('something.css') as scss ...
DRY. The core concept of Ruby, and the more I learn Ruby on Rails, the more I realize the importance of something like sass.
Clean superset of css and integrates easily with other packages being used.
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.
Sass is being used to keep our stylesheets organized in addition to the typical use cases (variables, mixins, functions, etc).
I won't write pure css anymore, after getting to know this nice preprocessor.
Sass is what CSS should have been. We use Sass to keep our stylesheets organized and to reduce duplication, making changes way easier.
All of our CSS is written in SCSS, Sass's CSS-like syntax. Variables, functions, mixins, and nesting are simply heaven compared to plain CSS.
Jekyll uses Sass. I like to use Sass. This stack now uses Sass.
I use sass only to @import my components to have a better readability than all stuff put in one page of css
Definitely nice to be able to nest your styling and not have to have separate blocks of CSS. We’re using a lot of media queries to make the site responsive.
Makes our CSS very maintainable by allowing for easily creating logical folder structures, variables and reusable mixins.