Welcome!

@DevOpsSummit Authors: Pat Romanski, Elizabeth White, Yeshim Deniz, Zakia Bouachraoui, William Schmarzo

Related Topics: @DevOpsSummit, Java IoT, Mobile IoT, Linux Containers, Containers Expo Blog, Agile Computing

@DevOpsSummit: Blog Post

Which CSS Preprocessor Should You Choose? | @DevOpsSummit [#DevOps]

We will focus on the two most commonly used in the industry: Sass and LESS

Which CSS Preprocessor Should You Choose?

With the growing number of CSS Preprocessors like LESSSassTurbineStylus andSwith CSS to name a few, it's hard to decide which to choose for your project, and which will provide the best CSS authoring.

Rather than focus on evaluating every CSS Preprocessor (that would simply take too long), we will focus on the two most commonly used in the industry:

Sass and LESS. We will provide a comparison on important deciding factors, like installation, features, and similarities & differences, to help you decide which is the best choice.

choosing a css preprocessor

Before we begin comparing... If you don't know much about CSS Preprocessors, I would recommend you first read this article: Ten Reasons You Should be Using a CSS Preprocessor to understand how they can make your life easier.

Which CSS Preprocessor should you choose

Installation
Let's start with the first fundamental step, installation. Both Sass and LESS are built upon different platforms, Sass runs on Ruby while LESS uses a JavaScript library.

Installing Sass: Sass needs Ruby installed to work. This comes pre-installed with Mac, but in Windows you'll need to install before you can start playing with Sass. Further, Sass needs to be installed through the Terminal or Command Prompt.

There are several GUI applications you can use in place of the terminal, like (Scout,compass.app)

To install Sass on the command line, run:

$ gem install sass

Or with npm (node package manger):

$ npm install sass

To run Sass from the command line:

$ sass input.scss output.css

Installing LESS: LESS is built on JavaScript, so installation is as easy as linking JavaScript library to your HTML document. There also are a few GUI applications to help compile LESS to CSS, most of which are free and perform very well (e.g. CRUNCHWinLess andLESS.app).

Alternatively, an easy way to install LESS on the server is with npm (node package manager), like this:

$ npm install -g less

To start the compiler from the command line:

$ lessc styles.less

Then, to run LESS from the command line, you can run:

$ lessc styles.less > styles.css

For a more comprehensive list of tools to compile LESS and Sass, look here, it covers a mix of both free and paid apps. There is a handy list of tools to make life a little easier when starting out with LESS or Sass, (25 Essential Sass and Less Tools).

Features
Here are the main features of Sass and LESS:

Sass

Less

VariablesExtend

 

Mixins

Nesting

Import

Operations

Functions

Loops

Partials

Compass

 

VariablesExtend

 

Mixins

Nesting

Import

Operations

Functions

Loops

Merge

Similarities and Differences
You can see from the features list above, the difference between Sass and LESS is not huge. Both offer a good range of options to help you write smart and efficient code.

The major differences between LESS and Sass are Variables, Inheritance, Looping Logic and Compass.

Let me explain further.

Variables
Variables are used to pre-assigned values (like colors, margins, padding, etc.) anywhere in your stylesheet. This enables quicker access, but is repetitive to implement, and more importantly, update.

If you use a variable you only have to update in one place.

In LESS, variable names are prefaced with the @ symbol. In Sass, variable names are prefaced with the $ symbol. In both, the value is closed with a semicolon, which is typical for CSS.

Example:

@myLessColor: #ff0087;p {color: @myLessColor;}__________________________$mySassColor: #ff0087;p {color: $mySassColor;}

The only issue in this example is Less's use of the @ symbol.

The @ symbol already has assigned meaning in standard CSS, whereas the $ does not.

This can be confusing for beginners unfamiliar with the standards of the language yet.

Mixins, Inheritance & Extend
Mixins in Sass and LESS are defined a bit differently. In Sass we use the @mixin directive while in LESS we define it with class selector.

Here is an example:

Sass/Scss

@mixin border-radius ($values) {border-radius: $values;
}
nav {
margin: 40px auto 0;
width: 760px;
height: 35px;
@include border-radius(5px);
}

LESS

.border(@radius) {
border-radius: @radius;
}
nav {
margin: 40px auto 0;
width: 760px;
height: 35px;
.border(5px);
}

Mixins in Sass and LESS are used to include properties from one ruleset to another. In Sass, this method is taken further with Selector Inheritance. The concept is identical, but instead of copying the whole property, Sass will extend or group selectors that have identical properties and values using the @extend directive.

Sass/Scss

.module {
padding: 10px;
h3 {
color: red;
}
}.news {
@extend .module;
}

Sass/Scss

.module {
padding: 10px;
h3 {
color: red;
}
}.news {
@extend .module;
}

Logic Statements
In LESS you can write a basic logic statement using a ‘guarded mixin' like this:

.boxcolor(@colour) when (lightness(@colour) > 40%) {
color: @colour;
background-color: #000;
.box-shadow(0 3px 4px #ddd);
}
.boxcolor(@colour) when (lightness(@colour) < 41%) {
color: @colour;
background-color: #fff;
.box-shadow(0 1px 1px rgba(0,0,0,0.3));
}

The equivalent in Sass, using if statements would be:

@mixin boxcolor($colour) {
color: $colour;
@if(lightness($colour) > 40%) {
background-color: #000;
@include box-shadow(0 3px 4px #ddd);
}
@if(lightness($colour) <= 40%) {
background-color: #fff;
@include box-shadow(0 1px 1px rgba(#000,0.3));
}
}

Compass
Both Sass and LESS have extensions for faster and easier web development.

Sass: has Compass on it's side, which contains a plethora of Mixins to write CSS3 syntax in less time. Compass extends way beyond just CSS3 Mixins. It has added other useful features like HelpersLayoutTypographyReset and even Sprite Images. It also has config.rb file where you can control the CSS output and other utilities.

It is an extremely useful all-in-one package for web development with Sass.

LESS: LESS also has several extensions, but unlike Compass (which has everything in one place), they are separated. Each extension is built by different group of developers. This won't cause problems for seasoned users, but could be troublesome for those starting out.

Here are a few LESS extensions that you might need to include in your project:

Conclusion
The CSS Preprocessor you choose - Less or Sass - is determined by personal preference.

Depending on the nuances most important to your project, choose the preprocessor that seems best. My personal choice is Sass, simply because of compass and the @ symbol in LESS always bother me. But, I would highly recommend you try both out and decide for yourself.

You can download Less here and download Sass here.

Also, for a more in-depth comparison of the 2 languages, here is some further suggested reading.

More Stories By Trevor Parsons

Trevor Parsons is Chief Scientist and Co-founder of Logentries. Trevor has over 10 years experience in enterprise software and, in particular, has specialized in developing enterprise monitoring and performance tools for distributed systems. He is also a research fellow at the Performance Engineering Lab Research Group and was formerly a Scientist at the IBM Center for Advanced Studies. Trevor holds a PhD from University College Dublin, Ireland.

@DevOpsSummit Stories
Atmosera delivers modern cloud services that maximize the advantages of cloud-based infrastructures. Offering private, hybrid, and public cloud solutions, Atmosera works closely with customers to engineer, deploy, and operate cloud architectures with advanced services that deliver strategic business outcomes. Atmosera's expertise simplifies the process of cloud transformation and our 20+ years of experience managing complex IT environments provides our customers with the confidence and trust that they are being taken care of.
Intel is an American multinational corporation and technology company headquartered in Santa Clara, California, in the Silicon Valley. It is the world's second largest and second highest valued semiconductor chip maker based on revenue after being overtaken by Samsung, and is the inventor of the x86 series of microprocessors, the processors found in most personal computers (PCs). Intel supplies processors for computer system manufacturers such as Apple, Lenovo, HP, and Dell. Intel also manufactures motherboard chipsets, network interface controllers and integrated circuits, flash memory, graphics chips, embedded processors and other devices related to communications and computing.
Darktrace is the world's leading AI company for cyber security. Created by mathematicians from the University of Cambridge, Darktrace's Enterprise Immune System is the first non-consumer application of machine learning to work at scale, across all network types, from physical, virtualized, and cloud, through to IoT and industrial control systems. Installed as a self-configuring cyber defense platform, Darktrace continuously learns what is ‘normal' for all devices and users, updating its understanding as the environment changes.
As you know, enterprise IT conversation over the past year have often centered upon the open-source Kubernetes container orchestration system. In fact, Kubernetes has emerged as the key technology -- and even primary platform -- of cloud migrations for a wide variety of organizations. Kubernetes is critical to forward-looking enterprises that continue to push their IT infrastructures toward maximum functionality, scalability, and flexibility. As they do so, IT professionals are also embracing the reality of Serverless architectures, which are critical to developing and operating real-time applications and services. Serverless is particularly important as enterprises of all sizes develop and deploy Internet of Things (IoT) initiatives.
The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long development cycles that produce software that is obsolete at launch. DevOps may be disruptive, but it is essential. DevOpsSUMMIT at CloudEXPO expands the DevOps community, enable a wide sharing of knowledge, and educate delegates and technology providers alike.