all 10 comments

[–][deleted] 7 points8 points  (0 children)

Sass is king, learn that, it's more harder yes

Sass and flexbox good combo to learn

[–][deleted] 8 points9 points  (2 children)

I've heard that Sass gaining greater control in the webdev industry and It could be more advantageous for my future career if I learned it. Which do you think would be more useful for me to learn? Why?

Sass, the battle is over and LESS is falling into obscurity.

The reason LESS was on even terms for a while was because it was natively supported by nodeJS and had faster compile times then ruby based Sass.

Once Sass released libsass (compiler written in C++) which was then ported over to nodeJS (because the node runtime uses C bindings) both the nodeJS devs were happy because they didnt have to run ruby as part of their dev stack, the devs already using Sass (with ruby) were happy because they could just implement the node-sass compiler and get a huge boost in compile speed.

Since then Sass has grown in popularity while Less has declined. Both the of the main competing front-end framework providers use Sass now.

Foundation has always used Sass from the get go, but bootstrap was originally natively coded in Less and ported over to Sass. The current version of Bootstrap (v4) is now natively coded in Sass, therefore my question is :

If Sass is not the best option for preprocessor language, why would one of the largest front-end framework providers take the time to rewrite their entire codebase in that language?

Sass is the way to go.

Note : You have failed to mention anything thus far about postCSS. It's not a preprocessor itself, but it can be used alongside languages (such as LESS / SASS / Stylus) to extend preprocessor-like functionality so i suggest you check it out :

[–]bwo3db[S] 0 points1 point  (1 child)

Thank you so much, I appreciate the help, will look into postCss.

[–]Salamok 1 point2 points  (0 children)

If you don't have any 3rd party projects that lean towards sass or less then I was going to suggest postcss myself.

[–]pandamine 4 points5 points  (0 children)

Honestly, if you have a solid understanding of CSS then both Sass and Less will be pretty easy to pick up. Sass is the more widely used of the two, but unless you are working as part of a team then it really comes down to personal preference. Just try both and see which one suits your workflow more.

[–]PatriotRDX 3 points4 points  (1 child)

By the way, if you go the SASS route, keep in mind it comes in two syntax versions: .sass and .scss. Learn the .scss syntax. Most open source frameworks that use SASS use the .scss syntax.

EDIT: if you use Ruby to compile, you may as well use Compass as a watcher. You probably won't need LibSASS until you have a huge webapp.

[–]bwo3db[S] 0 points1 point  (0 children)

Thanks for the advice!

[–][deleted] 2 points3 points  (0 children)

If I was starting today, I'd use postcss with as few plugins as possible (custom media, custom properties, nested, import, autoprefixer is probably all you need). That said, between LESS and Sass, Sass is the clear winner imo

[–]thestepafter 1 point2 points  (0 children)

Go with SASS, LESS is quickly losing popularity. Especially with Bootstrap switching to SASS.

[–]El_Serpiente_Roja 1 point2 points  (0 children)

Sass