I disagree - most of this post I wrote has very little to do with JavaScript itself and everything to do with Angular. Likewise, I don't want to come across as rude, but I also don't want words put in my mouth. The performance issues with Angular are not fiction, they are very real concerns. Hence the sheer number of tutorials popping up lately showing you how to use React in your Angular apps to improved the rendering performance plus a number of other hacks I'd prefer my juniors steer clear of.
It's also got nothing to do with the juniors coming from Python or Ruby, in fact most of mine started on Java and Erlang or are self taught, but I've had very little trouble with bad habits creeping in to projects with those same juniors when using frameworks like backbone, ember and react (so far) - so once again, it has very little to do with pitfalls in JavaScript and more to do with pitfalls in Angular itself - at least, that has been the case IME.
It's also got nothing to do with the juniors coming from Python or Ruby, in fact most of mine started on Java and Erlang or are self taught, but I've had very little trouble with bad habits creeping in to projects with those same juniors when using frameworks like backbone, ember and react (so far) - so once again, it has very little to do with pitfalls in JavaScript and more to do with pitfalls in Angular itself - at least, that has been the case IME.