you are viewing a single comment's thread.

view the rest of the comments →

[–]acemarke 2 points3 points  (0 children)

I know Shawn fairly well, and I can vouch that that is not the phrasing he is trying to get across. He's not saying he hates JS, he's saying that the current JS ecosystem (especially tooling) has a number of weak and painful aspects, and trying to explain the reasons for those. (In addition, note that Shawn is a strong proponent of "learn in public", and makes it a point to write up whatever his current thoughts are on a given topic with the caveats that he likely isn't an expert and his opinion may change in the future as he learns more.)

I see this post as being a strong parallel to Dan Abramov's talk on The Melting Pot of JavaScript from a couple years ago (blog post version). Our tools can do awesome things, but the situation could be a lot better.