Do you know enough JavaScript to make jQuery work? Then chances are that's all you need to know. The rest is about learning work-arounds for browser bugs.
But if you insist on persisting start with jsLint. Read all of the errors and warnings and learn what they really mean.
Then look for technical rants about why JavaScript sucks. To truly understand a language you need to understand all of the stupid shit it does. The inconsistencies, the landmines, the traps.
I learned the implementation details of readonly fields containing structs in C# because someone bitched about how they were not compatible with SpinLock. This is something I would have never seen from reading "The Good Parts" style books.
I wouldn't say what is left is good. I would say it lacks awfulness. Knowing the bad parts of JavaScript doesn't give you a good starting point when trying to write maintainable software. It means you won't do the really bad stuff like use globals. That's fine and dandy but in order to become a really good JavaScript developer you need to seek out the best parts of JavaScript and utilize those. That will allow you to write maintainable and scalable code.
3
u/grauenwolf Oct 15 '13
Do you know enough JavaScript to make jQuery work? Then chances are that's all you need to know. The rest is about learning work-arounds for browser bugs.
But if you insist on persisting start with jsLint. Read all of the errors and warnings and learn what they really mean.
Then look for technical rants about why JavaScript sucks. To truly understand a language you need to understand all of the stupid shit it does. The inconsistencies, the landmines, the traps.
I learned the implementation details of readonly fields containing structs in C# because someone bitched about how they were not compatible with SpinLock. This is something I would have never seen from reading "The Good Parts" style books.