Nice article. Two questions: SASS and SCSS are both mentioned for the same concept, is this intentional? SCSS looks like a pre processor for CCS, is this the way browsers implement this?
That was an indeed a typo error, which I've corrected thank you.
SASS & SCSS are very similar but are syntactically different. SASS doesn't have braces { } and ending semi-colons ;. No need to use @include for mixin, use + reducing keystrokes.
Nice article. Two questions: SASS and SCSS are both mentioned for the same concept, is this intentional? SCSS looks like a pre processor for CCS, is this the way browsers implement this?
That was an indeed a typo error, which I've corrected thank you.
SASS & SCSS are very similar but are syntactically different. SASS doesn't have braces
{ }
and ending semi-colons;
. No need to use@include
for mixin, use+
reducing keystrokes.And there are many more, do have a look at this article to better understand the differences.
thesassway.com/editorial/sass-vs-s...
And thanks again @jhelberg . Much appreciated.