4 ms·
I did read your comments, and I still think that you're making sass out to be entirely more complicated than it has to be. It's somewhat clear from your comment
by the_hangman 13y ago
I did read your comments, and I still think that you're making sass out to be entirely more complicated than it has to be. It's somewhat clear from your comments that you never gave css preprocessors a fair shake. There is no 'associated tooling' with sass. It's just a preprocessor. It doesn't need to integrate with your IDE (doing so would be somewhat pointless, IMO). You just invoke it from the CL and let it do it's thing. It really couldn't be any easier.
All of your problems are actually easily solvable, but it'd be rather pointless to use sass on a project that only has 5000 lines of css anyways. About as pointless as commenting on a thread about a technology you don't really understand to say that you "refuse to use" it, then trying to prove everyone wrong for pointing out that your issues with it are actually either not actually issues with the technology or have trivial solutions (i.e. you're not the first person to run into these issues).
- masklinn 13y ago> It doesn't need to integrate with your IDE (doing so would be somewhat pointless, IMO). It's somewhat neat, actually. Not necessary by a long shot but 1. there's a chance the IDE understands the precompiled languages (and offers syntax checks, autocompletion, etc...) and 2. you don't need to run the compiler/watcher because the IDE takes care of that when you or it saves, as part of its normal "stuff to do when saving".