Comments on: Musings on Preprocessing

By: Steven Sloan

Steven Sloan — Sat, 24 Mar 2012 18:50:21 +0000

@chriscoyier – Looks like Bryan added support for Jade a couple builds back – was getting frustrated with HAMLs lack of HTML includes myself – https://github.com/bdkjones/CodeKit/issues/98

By: Elliott the web design guy

Elliott the web design guy — Sat, 03 Mar 2012 07:53:46 +0000

I’ve only just started using SASS and my first impressions are pretty darn good, I love using mixins and @if’s are pretty cool, I am a one man band and don’t have a real need for a workflow that allows for multiple users to make changes to files however, because of reading this I can see the benefits and will start looking into setting up a proper workflow. As always amazing resource Chris thanks.

By: Klaus

Klaus — Sun, 26 Feb 2012 19:59:03 +0000

+1 for WebPutty. I’m using it just for SASS, now I’ll start digging Compass/Blueprint – I want to upgrade old code written for 960.gs.

By: Sam

Sam — Fri, 24 Feb 2012 12:46:39 +0000

I really love th idea of using LESS / SASS however I use Beanstalk to store mymain repo while devloping if I compile through codekit and then push to the server my team wont be able to get the LESS/ SCSS files they will see the compiled code, is there a way to compile on deploy to the main servers using Beanstalk.

By: Laurence

Laurence — Sun, 19 Feb 2012 09:07:14 +0000

I’m not sure you do have to work locally. My workflow consists of LESS + lessphp, which dynamically recompiles, minifies and gzips my LESS files whenever I call the stylesheet (which is at url.com/style.php as opposed to url.com/style.css). There is a little overhead with this processing, but when combined with caching the outputted CSS (if there are no changes to the LESS files) this is minimal.

Works for me!

By: Ray

Ray — Fri, 17 Feb 2012 02:20:49 +0000

I prefer the .sass syntax, too. No curly braces and semicolons everywhere = less typing, more readable, more fun IMO. Then again, I’m an old Pythonista ;)

Many people are not comfortable with the whole indentation-based thingy, though, or feel it strays too far from what plain CSS looks like. The good news is, both syntaxes are interchangeable, i.e. you can import .sass into .scss (and vice-versa) and it’ll compile without conflict. SASS even comes with a command line tool to convert source files between the two flavours, should your tastes change.

By: Derek

Derek — Thu, 16 Feb 2012 21:10:13 +0000

If you are using SASS in conjunction with Compass, Compass has an option to compress your code when you process it. Very handy stuff.

By: T.Cretin

T.Cretin — Tue, 14 Feb 2012 01:39:52 +0000

@tommy, you ever read those one paragraph comments which have nothing constructive to add to the conversation, only to bash someone else who actually has an opinion? It’s a waste of precious electrons.

By: Jay

Jay — Mon, 13 Feb 2012 01:19:11 +0000

One massive advantage of using LiveReload with it’s new script method is getting auto-refresh on iOS simulators (including soft-refresh of CSS). That is pretty much the best reason to use it.

By: Kenneth White

Kenneth White — Sun, 12 Feb 2012 19:00:41 +0000

I can speak to that as a former designer turned developer who is just getting into command line. For me it boiled down to the worry that command line is a direct tap into my computer, and unlike the operating system and its friendly UI, command line operations aren’t safe from me—the worst part of the computing cycle. The sentiments I hear from fellow designers are similar, “I don’t want to accidentally destroy my computer.”

I think it’s getting better and you nailed it on the head. Designers and front-end devs just have to be shown that it’s all gonna be okay.