Hacker News Reader

Writing personal projects in a personal way seems just fine to me :) Looking at that file it's very obvious what's happening after just a cursory glance. I'd much prefer code that's very easy to understand without semicolons than the opposite.

Even though people have downvoted you, personally I agree with you, I haven't added any semicolons to main.js though because that file was automatically created in the original project I forked, if I ever have to edit it I will add the semicolons as I'm there but I haven't touched that file yet.

That file is a copy of a stock one from the quickstart guide: https://github.com/electron/electron/blob/master/docs/tutori...

Might as well die on the hill of tabs vs spaces or single-quotes vs double-quotes or trailing commas or space after function name.

More useful advice would be: use Prettier and ship a .prettierrc so people can trivially transform their contributions into code consistent with the rest of the project.