I am against the use of linter in the context of teaching. Linters are tools to aid production, in the context of teams with differently skilled developers. Teaching should be more about facts, and not shortcuts.
The ECMA-262 standard is a better source of information, IHMO, or the excellent series by Dmitry Soshnikov. see section #7.9.1/7.9.2 of ECMA-262 standard. On Jan 13, 2012, at 12:57 AM, Lars Gunther wrote: > Hi again > > It seems I have evangelized quite a few fellow teachers in Sweden that > JavaScript makes a good first language when learning how to program. > > However, most teachers have been using Java, C++, PHP or VB + some Pyhon and > C#. When they start to teach JavaScript they will encounter stuff they hardly > understand themselves and that is hard to explain to students. They also do > not yet know about JS-specific style guides and JSLint/JSHint. > > I am trying to set up page documenting the most confusing behavior in JS. > It's a WIP, but if anyone can spot errors and make useful suggestions about > what to add, I'd be very grateful. > > https://github.com/itpastorn/programmering-1-med-js/blob/master/javascript-quirks.markdown > > > > -- > Lars Gunther > http://keryx.se/ > http://twitter.com/itpastorn/ > http://itpastorn.blogspot.com/ > > -- > To view archived discussions from the original JSMentors Mailman list: > http://www.mail-archive.com/[email protected]/ > > To search via a non-Google archive, visit here: > http://www.mail-archive.com/[email protected]/ > > To unsubscribe from this group, send email to > [email protected] > -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
