This is the first of a series of posts that aim to make your life easier and enhance your productivity while developing websites, by giving you use...
For further actions, you may consider blocking this person and/or reporting abuse
But still not working on IE11, i would totally prefer CSS variales, but Internet explorer compatibility is a must for me.
You can use custom properties even on IE 8. You will just loose the ability to change them runtime, like sass. Search fo PostCSS because learning sass in 2018 is “meh”.
But we're on another scope there. Here, we're talking about simple easy cheesy css, with some extra tools, opposing to a tool for dinamically creating and modifying css. I agree it's all within the business requirements, but usually with sass you dont need to learn javascript at all to create complex styling solutions.
Thanks pabloKz.
I've never bothered to check out SASS until I read this.
It seem to make CSS files more manageable without having to repeat the same style over and over.
I use to be a huge disciple of SCSS, but nowadays my opinion has shifted. I feel like it can be dangerous how easy it becomes to deeply nest hierarchies -- you can easily end up creating selectors that are needlessly specific. CSS is a lot more capable now, and with web components, I think there is a valid case to be made for separating concerns according to components and their functions vs a strict separation between JS/HTML/CSS. I am also a terrible at CSS FWIW :P
Thank you, I've been meaning to look into SASS and your post was get helpful!
This is exactly my point!
Man, to compile sass you need ruby-sass or node-sass (js) or some external shitty tool like prepros or codekit. This is a no-sense even because sass is not css at all since it use his own syntax. With postcss you can write standard css and get... css. And don’t forget that if you are using autoprefixer (and you should) you are already using postcss.
Wut? Do you know what autoprefixer do?