alerante has quit [Remote host closed the connection]
bghost has joined #nanoc
whk has left #nanoc [#nanoc]
bghost has quit [Ping timeout: 252 seconds]
bghost has joined #nanoc
bghost_ has joined #nanoc
bghost has quit [Ping timeout: 245 seconds]
jadd_ has quit [Quit: Leaving...]
bghost_ has quit [Quit: leaving]
jadd_ has joined #nanoc
skroon_ has quit [Read error: Connection reset by peer]
skroon has joined #nanoc
bghost has joined #nanoc
bghost has quit [Ping timeout: 240 seconds]
bghost has joined #nanoc
bghost has quit [Ping timeout: 272 seconds]
bghost has joined #nanoc
bghost has quit [Ping timeout: 245 seconds]
bghost has joined #nanoc
bghost has quit [Ping timeout: 240 seconds]
skroon has quit [Read error: Operation timed out]
skroon has joined #nanoc
<musicmatze>
ddfreyne: On the sass thing: Isn't Sass optional in nanoc? If it is, I wouldn't do anything! I would tell the user (in the docs or somewhere) that sass takes long time but is optional...
<musicmatze>
Its not your job to speed up sass or so! Your job is to compile content into html, sass (-support) is just a neat additional you ship!
jadd_ has quit [Quit: Leaving...]
jadd_ has joined #nanoc
jadd_ has quit [Ping timeout: 272 seconds]
jadd_ has joined #nanoc
jadd_ has quit [Ping timeout: 272 seconds]
jadd_ has joined #nanoc
jadd_ has quit [Ping timeout: 240 seconds]
skroon has quit [Read error: Connection reset by peer]
skroon has joined #nanoc
jadd_ has joined #nanoc
jadd_ has quit [Ping timeout: 272 seconds]
jadd_ has joined #nanoc
<ddfreyne>
musicmatze: True, but nanoc can (and should) be smart about when to recompile or not
jadd_ has quit [Ping timeout: 272 seconds]
<ddfreyne>
musicmatze: Also, if the sass filter itself is taking a lot of time (not just the sass filter) then something needs fixing
<musicmatze>
Okay, I thought you were talking about the sass gem. But if it is nanoc internal, ...
* ddfreyne
has been writing some Go code this weekend!