On Sat, Feb 25, 2012 at 12:25 AM, Joe Developer <[email protected]>wrote:
> No one is forcing anyone to use anything ( your work environment may vary >>> ) - but the simple math is this: JS is going to be everywhere, lots of >>> people will be coding in JS, demand for expertise ( or competence, or >>> ability to gain it ) outstrips supply. Perhaps we have now established a >>> population and a level of access to means for knowledge transfer of >>> sufficient quality for 'the masses' - I doubt it. >>> >>> There will likely always be a population that will see benefit from >>> using jslint, whether as blindmans cane, training wheels, fast-fail >>> indicator or code consistency enforcer. >>> >> >> I don't disagree - I just want it more configurable to my/our "house >> style". Because I find it useful that it does catch some errors (there's a >> large class of errors for example that "use strict" doesn't catch until >> runtime, which is annoyingly late - I'd like a jslint that can catch those >> errors, without futzing with my style - it seems clojure compiler might >> just do that though). >> > > Well, isn't that the motivation behind jshint? > Absolutely... I just don't think it goes far enough yet. > Considering that jslint is both opensource and written in JS getting it to > do what you want shouldn't be a challenge for the coding mastery that > informs your stylistic mojo. > You're right. But I'm lazy :) All I'm saying is that I wish there were better tools. And yes I should probably write them (or help write them). But then we circle around to the laziness :) Matt. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
