If you can't make something like sass work with your version control, it's a problem with your workforce or workflow, not the technology. It is trivial to set up a ruby command line on any OS and then have a .gemfile in your version control to ensure that everyone is using the same version of sass. Then all that is required to generate the css files from the sass sources is opening up a command prompt with ruby and typing `compass watch`. It's worth it for the time saved writing css.
> Nope but it's a real problem. Some of our guys don't do the web.
Is it not also a problem that you have people writing your css who "don't do the web"? That seems like the bigger issue here to me.
If you read my comments carefully, you will see this is a merge time issue. Many different people do merges. Some reintegration merges will be performed by people who don't do web stuff. There may be trivial web changes on a feature branch but people have absolutely no idea about Sass or associated tooling. They can cope with css fine.
Our product has about 5000 lines of css and about 3 million lines of other languages. Web is a tiny part of our applications.
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).
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".
Not part of VS proper but if you can use extensions it's a good alternative. I haven't used it unfortunately as my work doesn't really keep me in VS for web dev but the tooling should be rather decent from what little I've touched. YMMV though, obviously.
Doesn't change what I wrote.
> Regeneration is a problem when you have lots of developer workstations, build agents and test machines to deploy the Sass stack to.
It's no more a problem than all the other stacks you have to deploy. And if you can't deploy any stacks, maybe that is the core problem.
> Nope but it's a real problem. Some of our guys don't do the web.
They won't be able to merge HTML, CSS or JS any more reliably than Sass or Less, why are they doing those merges? Do you also ask designers to merge WPF?
But I can't write C# in it.
> There is no reason or justification for merging the CSS. Merge the source, regenerate.
Regeneration is a problem when you have lots of developer workstations, build agents and test machines to deploy the Sass stack to.
> That's not a problem with Sass or Less or whatever.
Nope but it's a real problem. Some of our guys don't do the web.
> At the cost of increased maintenance effort.
Well the maintenance effort went up to unacceptable amounts for us so I don't believe that.