Following up my post about validating your HTML, here comes some alternatives to the tools that I suggested in the first post!

Alternative validator: vnu.jar

There's another validator called vnu.jar. Check out the vnu.jar web service, vnu.jar website and source code. It's very easy to install.

There's a Grunt plugin to use vnu.jar as validator: grunt-html.

Alternative build system: Gulp

gulp-w3cjs works with W3C.js under the hood just like grunt-html-validate. It does not yet have an option to use a locally installed validator. Any takers? :)

HTML, what's the point?

Finally, I've heard from a reader that doesn't see the point in validating HTML was missing reasons for why we should validate HTML:

I do miss a discussion about the *value* of validating HTML. You seem to simply assert that it is valuable, but without some kind of justification for why you should do it, validating HTML is IMO just cargo culting.

Or to put it in another way: You should reflect on the question of why many (most?) don’t bother validating their HTML. Is it because the ROI is too insignificant?

Here's a great answer provided by Anders Ringqvist:

HTML validation is *not* cargo culting. If I got a dollar for every time I fixed/answered someones problem/question about a layout problem that was only bad nesting of tags I would be richer than Mark Zuckerberg. Not validated HTML is a time vampire for your dev team. Of course if you only do open source and have all the time in the world or do solo dev then by all means.