<ddfreyne>
guardian: Will get to it either this evening most likely
<guardian>
oh I'm sure you will
<guardian>
but the more the feedback the better right?
<guardian>
which of rubypants vs typogruby do you recommend? (yeah there's fast-aleck but I'm targetting stable filters for that project)
<bobthecow>
guardian: they're both *really* slow.
<bobthecow>
like, 8 level deep nested regex replacements across the entire contents of your pages slow.
<guardian>
ok
<bobthecow>
if you're going to use something other than fast-aleck, then only process the minimum amount of each page.
<bobthecow>
use the filtering helper.
<bobthecow>
rather than processing the whole page for each item.
<bobthecow>
oh, or filter before laying it out.
<bobthecow>
that could work too.
<bobthecow>
i've been using fast-aleck for years, and it's stable enough :)
<bobthecow>
fast aleck is ~100x faster than typogruby.
<bobthecow>
typogruby is ~20x faster than rubypants.
<guardian>
yeah but fast aleck requires building from source
<bobthecow>
but that's because rubypants is a superset of typogruby.
<guardian>
all members of the team can't do that
<bobthecow>
rubypants does everything typogruby does, plus mroe.
<guardian>
or... I provide a vagrant based VM for authoring doc
<guardian>
I had the impression typogruby did everything rubypants does + more
<bobthecow>
or you switch the filter on/off based on existence of fast aleck
<bobthecow>
oh, sorry, that's what i meant.
<guardian>
and fast-aleck does all what typogruby does?
<bobthecow>
yeah.
<bobthecow>
fast aleck is 2000x faster than typogruby.
<bobthecow>
100x faster than rubypants.
<guardian>
ok
<bobthecow>
fast aleck exists because of how painful it was to compile large nanoc sites with typographic enhancements :)
<guardian>
I'll consider that... I'm hesitating providing coworkers with a VM because I have the impression it's going to fall down when they try to compile our new nanoc base docs under Windows :)
<guardian>
so if it's me configuring shit on the VM it's ok I can bring fast-aleck in
<bobthecow>
does everyone have to compile the real thing?
<bobthecow>
or do most people just compile for testing, local preview?
<bobthecow>
because if that's the case i'd turn off the typographic enhancements if the user doesn't have fast aleck installed.
<guardian>
actually 3-5 people are concerned, the two tech writers have a windows laptop
<bobthecow>
but do *they* compile the real production version?
<guardian>
well the two tech writers yes
<guardian>
because they want to see how the final deal looks
alerante has joined #nanoc
<guardian>
so they want typographic enhancements
<bobthecow>
gotcha.
<guardian>
well they can opt out to go faster, but likely at some point they want to see the final thing
<bobthecow>
make it ENV based then?
<bobthecow>
$ ENHANCE=1 nanoc compile
<guardian>
yeah
<guardian>
too bad nanoc doesn't support defining options on the CLI :)
<bobthecow>
it does'
<bobthecow>
ENHANCE=1 nanoc compile :)
<bobthecow>
are your windows users running a sane shell at least?
<guardian>
it's cygwin
<guardian>
the shell's ok
<bobthecow>
okay. so that'd work.
<guardian>
it's the cygwin + ruby + imagemagick chain which is a train wreck
<guardian>
for example
<bobthecow>
oh, i can imagine.
<bobthecow>
why not vagrant + VM + awesomeness it up then?
<guardian>
I guess a VM is okish, and more experienced users will be on their own which is equally ok
<guardian>
well of course I'll iron things out
<guardian>
yeah I need to learn more about vagrant
<bobthecow>
vagrant is 100% rad.
<guardian>
because I would like to use crunchbang
<guardian>
and there doesn't seem to be provisioned crunchbang vagrant images available
alerante has quit [Ping timeout: 240 seconds]
<guardian>
also I'm not quite sure in my situation vagrant makes a big difference between downloading a VirtualBox VM from our LAN, or does it?
<bobthecow>
vagrant is virtualbox vms.
<bobthecow>
vagrant is a set of shell scripts, configuration and workflows around virtualbox vms.
<bobthecow>
part of that is the build stuff, but you can prebuild them and just distribute the VM if you want.
<guardian>
hence my question... I can install crunchgang, aptitude update, install ruby and nanoc and gems. And share that
<guardian>
without vagrant
<bobthecow>
vagrant isn't awesome because it can build VMs.
<guardian>
but I'm still curious about it, and I'll use my week off next week to learn it
<bobthecow>
it's awesome and also it can build VMs
<bobthecow>
that's a bonus, not the reason to use it.
<bobthecow>
the reason to use it is because you open a folder, type `vagrant up` and it boots your VM. then you type `vagrant ssh` and it sshs into it.
<bobthecow>
binds ports so you can `nanoc view` with a browser on the host os.
<bobthecow>
etc.
<bobthecow>
the part about it building a VM is just one piece.
<guardian>
ok
<guardian>
now that makes sense
<bobthecow>
*but*
<bobthecow>
i'd recommend building your VM with it anyway :)
<bobthecow>
it's like automating your tests. it forces you to make a process out of it, which means it's free every other time you need it.
<bobthecow>
i watched a talk once where a systems guy said "you need to make it so your servers aren't precious anymore"
<bobthecow>
you shouldn't care if your VM breaks, because you should have already automated making a new one.
<bobthecow>
if you build it manually, you'll have to build it manually again when you want to do something different.
<bobthecow>
if you build it with a script, you change the script and build again.
<guardian>
yeah that's sound
<guardian>
in that vein, I also have Docker to run