Meh, the documentaiton on the README says which shims do not work. Any competent team member should be able to "know" the sensible subset of ES5 from reading that.
Well, I work on a project with four frontend developers and some more backend devs. Now how often do you think it happens that a backend dev says (to himself only, otherwise I could slap him beforehand): "Ah, there's only a minor part of that javascript that needs changing, I can do that for myself." And then we end up with code that does not match the styleguide, has several nested try..catch blocks, has objects with getters and setters that don't do anything different than a direct access of the properties and so on (in short, javascript the java way).
These guys would never read documentation. We have a large set of documentation on the architecture and styleguide and best practise of frontend development, and somewhere in there I put "If you read this, come to me and you get some sweets". Of all the people in our team, only one read this.
OK, this got more of a rant than I intended. In short, teams seem to have incompetent developers as well, and so using shims that do not match the spec is a risk.
Matt -- Follow me on twitter.com/gweax -- 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]
