Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
kunashe21423yI too was initially excited but found that styling I made for one project could not be easily used in another.
Deeply nested sass means your markup needs to have the exactly the same nesting hierarchy otherwise bad shit happens.
It has a learning curve.... Started with the same reactions and outcomes (very specific css) this made me learn out to correctly inherit CSS...
After a while and after it solves you some pretty weird things with ease you will come to love it
(PS I am not a designer, just did not like my team's designers - really shitty structuring)
haabe14123y@mmcorreia although I see that it gets things done easier than just coding regular CSS, I can't say I've fallen in love with it.
It feels so, I don't know, immature. I've ended up with quite a complex system of loops, maps and mixins to complete my breakpoint needs, but it doesn't look good. Does the job, though.
@haabe that I wish too... It takes a different thought process to make good CSS and if it was closer to structured programming it would be so much better. I'm with you in that...
I'm just saying: don't label it just yet. It made things easier and more maintainable for me more than it hasn't but you know that with every knew framework your first dives are the weirdest