Posts

Showing posts with the label JSLint

My Last Comments On JSLint

Preface I have been working with many teams and I have used JSLint on daily basis. This post is not about the tool itself, neither against Douglas work, this post is about developers often too religious about this tool . Finally, if you follow this blog you have already read tons of other reasons to think rather than " suffer silently this tool ". It's my last post about it and I hope " it will not hurt your feelings ". Seriously guys, it's not that I think JSLint is all bad, but I cannot stop thinking it's simply an effect . The more I hear or read about developers being so religious about this tool, the more I feel to blame it . I am pretty sure Douglas will hate me for this post but I really hope he will read it 'till the end. Douglas Talk At Falsy Values Both me and big Doug were there , me for a workshop and Mr D. for his speech. " Surprisingly " Mr Crockford talked about JSLint (again?!) and why it's so good. While many hints fo...

JSLint: The Bad Part

Every programming language has somehow defined its own standard to write code. To be honest, as long as code is readable, clear, and indented when and if necessary, I think we do not need so many "code style guides" and, even worst, sometimes these "code standards" let us learn less about the programming language itself, helping if we are beginners, sometimes simply annoying if we are professionals. Disclaimer This post aim is absolutely not the one to blame one of my favorite JS gurus, this post is to inform developers about more possibilities against imperfect automation we'll probably always find in whatever excellent spec we are dealing with. This post is about flexibility and nothing else! JSLint And Code Quality Wehn Mr D says something, Mr D is 99.9% right about what he is saying ... he clearly represents what we can define a Guru without maybe or perhaps but he, as everybody else here, is still a programmer, and we all know that every programmer ...