Also, leaving out semicolons in JS is a bad idea, and no amount of hipwashing will change that fact.
Style is important, within one project, but outside of that? There are source formatters to keep your project consistently formatted.
With style fixes you don’t solve the actual problem with JS where most websites nowadays try to send you megabytes of cruft you don’t need.
Is what was said about rollup.js actually true? Does it really add anything beyond the other tools? I can’t tell if it’s hyperbole or the truth.
If it’s real, then that’s really petty and horrifying.
I can’t speak to the points in the article, but Rollup uses ES2015 modules and consequently does tree shaking. This is now part of webpack2, but Rollup seems to have popularized the idea which IMO is more than enough to justify it’s existence.
So, according to the article, the reason there is a lot of “rework” in JS libraries is because developers dislike each other’s code style. But no actual evidence is presented for this odd claim.
As a specific example, the article claims that Rollup was only created because the author didn’t like Browserify’s style. That is an extraordinary claim, given the technical sophistication of Rollup’s tree shaking approach. And again, no evidence is cited.
I love style guides and linters to enforce them, but this article is just baiting the “get off my lawn” crowd.
Everyone seems to take everything I write so literal. I wish I was better at conveying hyperbole and sarcasm better. I think developers tend to be more analytical, and stuff tends to just go over their heads. Some people get it. Some don’t.
I’m not trying to bait anyone. I just wrote what was on my mind, in a style I talk to my dev friends in.
Thanks for reading.
@drewh sorry for misunderstanding your post. Unfortunately, the style read as “crazy rant,” not “tongue in cheek” to me. It would probably help if the article had been tagged satire. Communicating between humans in text is hard, especially when humor is involved. :-/