Sass- A utility with a darker side
A potential increase in the number of steps involved in the development life cycle
Too many syntaxes create compatibility issues
File Size of resultant CSS is way too different from what you are expecting
- You may opt for lopping in a CSS pre-processor and generate n items wherein only one is visible. All the remaining items are hence listed in the resultant, static CSS file.
- The final CSS has a flattened hierarchy with a tree of selectors duplicated for each individual selector.
- While using some specific CSS pre-processors, you can do away with writing the vendor prefixes. While this can save you some valuable project time, you might forget that a single attribute would be expanding into 5 or 6 within the final CSS.