Earlier quoted context omitted.
I'm sure it wouldn't be a stretch to write an extension for Brackets that allows you to handle templates more effectively. On another note, you'd be surprised how many people are still doing pure vanilla. Preprocessing isn't usually part of a beginners toolchain, you gotta learn the underlying part first before you start grafting on the preprocessors used in larger projects.
We've actually stopped using all pre-processor for everything we do for Segment.io[1] as well, and we're not beginners. One of the biggest problems with them is that you immediately eliminate a huge portion of the people who are willing to contribute to your code if you select a pre-processor they aren't fond of. It's fine for app internals, but for sharing small[2] open-source[3] components[4] it's not a good idea—w…
components/
widget-one/
template.html
script.js
style.css
widget-two/
template.dust
script.coffee
style.styl
And then the style file for a component is completely scoped to that component's main class: .widget-two {
.widget-two-control { color: blue; }
}
The build script can handle each component separately and stitch the results together. Just because SASS/compass encourages a monolithic style doesn't mean it's necessary.