I remember saying in 2008/2009 that IE and Opera (because it used the same or similar JS engine) had some of the best reasons for failing with regard to badly c

I remember saying in 2008/2009 that IE and Opera (because it used the same or similar JS engine) had some of the best reasons for failing with regard to badly coded JavaScript. I would always just open up IE to check to see if my code was "valid" even when I wasn't targeting IE specifically. Just swallowing errors is not good practice, but I can't say that I noticed this in Chrome, tbh. I can say that Chrome's dev console is better than Safari's/Webkit's. Chrome isn't my default browser, I really only open it for flash content and to debug a site's JS when Safari isn't giving me the info that I need. I agree with the overall tone of the article -- (mobile) Safari is a decent browser, and in a lot of ways, a better experience for both the user and developer than Chrome. In some ways it isn't.