3 ms·

Actually no it doesn't work like that. It's really a pain in the arse for windows users like myself who are part of more than a one man team. What happens is,

by csmuk 13y ago

Actually no it doesn't work like that. It's really a pain in the arse for windows users like myself who are part of more than a one man team. What happens is, you get three options: 1. Deploy Ruby, Sass and associated dependencies to every workstation, build agent, test machine etc. Deploy tooling and build integration to the above so that any changes to .sass files in the IDE and build process get reflected on disk in the VCS. Educate every developer who touches the project on what they are, how to manage them effectively, the rules around merging etc. -or- 2. Do the above but ship the entire Ruby VM and libraries in your VCS. -or- 3. Get random build failures company-wide, old versions of generated CSS files and crap floating around and being checked in by developers, half arsed merges and just pain. I'll pick option (4) which is don't use it. I've been at ALL of the above steps. We have removed it from our product. Life is better now.

egypturnash 13y ago
Here's an option you haven't tried: 5. Use CodeKit[1] on the Mac, and similar tools for Windows. I can't tell you which ones on Windows are the best but damn it sure is nice to just casually write SASS/LSSS and have it get compiled when you save it because the compiler's sitting there watching for file changes. 1: http://incident57.com/codekit/ http://incident57.com/codekit/ 2: https://www.google.com/search?client=safari&rls=en&q=codekit+for+windows&ie=UTF-8&oe=UTF-8 https://www.google.com/search?client=safari&rls=en&q=codekit...
castis 13y ago
Sucks you guys couldn't get it to work. LESS has made our lives easier. We have a LESS parser in javascript that gets put in place of the css includes in a dev environment. When deployed, that whole block is replaced by css that was compiled at the build point.
lmm 13y ago
> Deploy Ruby, Sass and associated dependencies to every workstation, build agent, test machine etc. Deploy tooling and build integration to the above so that any changes to .sass files in the IDE and build process get reflected on disk in the VCS This should be easy. If it is hard that means your deployment/ops infrastructure is inadequate, and you should fix that now rather than after your build machine suffers a hard disk failure. > Educate every developer who touches the project on what they are, how to manage them effectively, the rules around merging etc. You don't edit files that aren't in VCS; if some files are ignored you assume there's a good reason for it; you edit the source version, and you merge the normal way you merge source. These are all standard rules of development that every developer should know. I guess using sass means every developer needs to learn sass, sure. But in terms of how quickly you can learn, and how much time it saves you over editing raw css, that pays for itself in like an hour.

by csmuk 13y ago

egypturnash 13y ago

Here's an option you haven't tried: 5. Use CodeKit[1] on the Mac, and similar tools for Windows. I can't tell you which ones on Windows are the best but damn it sure is nice to just casually write SASS/LSSS and have it get compiled when you save it because the compiler's sitting there watching for file changes. 1: http://incident57.com/codekit/ http://incident57.com/codekit/ 2: https://www.google.com/search?client=safari&rls=en&q=codekit+for+windows&ie=UTF-8&oe=UTF-8 https://www.google.com/search?client=safari&rls=en&q=codekit...

castis 13y ago

Sucks you guys couldn't get it to work. LESS has made our lives easier. We have a LESS parser in javascript that gets put in place of the css includes in a dev environment. When deployed, that whole block is replaced by css that was compiled at the build point.

lmm 13y ago

> Deploy Ruby, Sass and associated dependencies to every workstation, build agent, test machine etc. Deploy tooling and build integration to the above so that any changes to .sass files in the IDE and build process get reflected on disk in the VCS This should be easy. If it is hard that means your deployment/ops infrastructure is inadequate, and you should fix that now rather than after your build machine suffers a hard disk failure. > Educate every developer who touches the project on what they are, how to manage them effectively, the rules around merging etc. You don't edit files that aren't in VCS; if some files are ignored you assume there's a good reason for it; you edit the source version, and you merge the normal way you merge source. These are all standard rules of development that every developer should know. I guess using sass means every developer needs to learn sass, sure. But in terms of how quickly you can learn, and how much time it saves you over editing raw css, that pays for itself in like an hour.