There's no real good reason why, but my mild OCDish tendencies get intensely triggered by looking at Javascript with no semicolons.YOU'LL PRY THEM FROM MY COLD, DEAD HANDS FIRST. I started skimming the rules and was like "this all seems fine" and then noticed "no semicolons".The no semicolons and space after function name are really the weird things here.No semicolons, two space indentation, space after function name, single quotes for strings? There's no way this would fly with a majority of developers.If there was an actual gain to leaving out the semicolons, I'd be onboard but the only gain here is someone's aesthetic pleasure and someone else's aesthetic displeasure.Why do these people want to avoid semicolons at all costs? Even inconsistencies? Even potential bugs? Why? I just don't get it.The JavaScript Standard Style TL:DR (source: )Īlthough it appears to have been in the works for about a year, it was just introduced on the coding forum site Hacker News today, where semicolons emerged as a big sticking point, judging from comments such as: Saves precious code review time by eliminating back-and-forth between maintainer and contributor." Catch style errors before they're submitted in PRs.The easiest way to enforce consistent style in your project. Enough of this madness! This module saves you time in two ways: "No one wants to maintain multiple hundred-line style configuration files for every module/project they work on. "The beauty of JavaScript Standard Style is that it's simple," the project's README.md states. The JavaScript Standard Style project on GitHub (and here on the Web) promises "one style to rule them all." A fledgling effort to promote a new standard for styling JavaScript code is getting hung up on the issue of whether or not to use semicolons over at Hacker News.
0 kommentar(er)
