<tom[]>
my response was "why is nanoc in the linting business?"
<tom[]>
because that's what it looks like and i don't know why nanoc does this
_br_- has quit [Ping timeout: 244 seconds]
_br_ has joined #nanoc
leobalter has left #nanoc ["tchau"]
cDlm has joined #nanoc
_whitelogger has joined #nanoc
tantalum has quit [Quit: Leaving]
<ddfreyne>
tom[]: Oh, all changes that make it into nanoc go through a code review
<tom[]>
oh man. the very thought of ruby code reviews
<tom[]>
so glad i don't have to do that
<ddfreyne>
tom[]: how come?
<tom[]>
well, i don't know much ruby but i have the impression the language design had as one if it's main goals to allow the same thing to be coded in as many ways as possible
<tom[]>
so i imagine if you want a certain kind of thing to repeatably appear a certain way (highly desirable in my view) then you must have a *lot* of style rules
<ddfreyne>
tom[]: There are automated style checks, so the code review doesn't have to bother with that
FabianB has joined #nanoc
<tom[]>
then aren't there endless discussions on the linter's config?
<tom[]>
people seem to get more emotional about style than anything else
FabianB_ has quit [Ping timeout: 244 seconds]
<ddfreyne>
tom[]: I don’t think we’ve had a single discussion so far
<tom[]>
anyway, i still don't know why nanoc does css and html validation
<ddfreyne>
tom[]: It doesn't do the HTML/CSS validation itself; it delegates to a library for that
<tom[]>
naturally
<ddfreyne>
tom[]: It's good to have valid HTML and CSS
<ddfreyne>
tom[]: Same for internal links etc. Makes sure you don't accidentally deploy broken sites
<tom[]>
so is it for checking input or output?
<ddfreyne>
It can do both, but it's mostly usefulf or output