re: Finding Bugs in Languages/Frameworks You Don't Know: node.js VIEW POST

re: as a standard you should add a semicolon This is also an opinion. Semicolons are absolutely optional. The first thing I do in a new project is...

I feel like you're having me repeat myself:

you personally feel it's unnecessary.

You realize that the world doesn't run on your personal build preferences, and that every third party library you're describing is not a language feature, right?

Requiring external dependencies is not a solution.

It's also not because you personally have a different build process, that the problem doesn't exist.

Since your theories are in direct conflict with my real world experience, and you refuse to actually run a real test to see what I am saying is correct, I don't see how this conversation can continue.

I feel like you're having me repeat myself:

Instead of continuously repeating yourself, if you were to attempt to actually create a repo you would see this for yourself.

One of us is correct and one of us is wrong. People reading this thread can test this for themselves to see who it is.

But I'll repeat myself for the final time for any other person's that stumble across this thread in the future and want the correct answer.

Since I started writing JavaScript, back from 1996 to today, with or without a build system, semi-colons are completely optional. with the exception of naked expression example mentioned in my original comment.


Let me ask you this, Joel:

Is there any security implication from omitting semicolons? Is it safer to use semicolons? I do not know the answer right now, or whether or not it matters, but I think this is something worth exploring.

Not that I am aware of. But if there were, it would be a game changer in the semi vs no semi debate. So I think if one was found, it would make big news.

If you minify your code, or webpack or roll-up, or Babel, then semi-colons will be added to the dist bundle anyway.

So develop in the style you prefer, use prettier and ESLint to enforce your chosen style and don't stress about it 😁


Since your theories are in direct conflict with my real world experience

I've seen this problem happen in production with actual clients.

Since I started writing JavaScript, back from 1996

...ok. I'll leave you to your mental masturbation. We were talking about language implementations of semicolons, not how old you are.

For anyone that reads this thread: Know the language's implementation and consequences. It's a reasonable thing to expect you to know, and it might come up in an interview. Personal opinions don't matter much if you're asking for the answer to 1 + 1. Toolset iterates constantly and tools disappear sooner rather than later - it's JavaScript that stays. Learn from first principles.

code of conduct - report abuse