My interpretation of "hipster" is being different because you think it's cool to be different. Being different because you think it's a better approach is called "making progress", either because you'll be proven right or proven wrong.
I've thought about the de-facto standard way a lot and I think that it does nothing to avoid bugs while potentially misleading a coder about the language. Therefore I think it's worse.
The only reason I follow the de-facto standard is because the time spent arguing about it with my peers is better spent getting work done.
Nobody has any good reasons that apply to most people, both for and against semicolons. There really isn't a huge difference in either style except in rare cases.
> The only reason I follow the de-facto standard is because the time spent arguing about it with my peers is better spent getting work done.
Which is why that is an excellent reason. Standards are useful, so if there is one, stick to it. If there is no reason to go against the standard, then don't.
> I think that it does nothing to avoid bugs while potentially misleading a coder about the language. Therefore I think it's worse.
Not seeing any semicolons can also potentially mislead about the language. It is not worse, they are both misleading until you realise ASI exists.
Omitting semicolons also does nothing to avoid bugs, and introduces a different (additional?) set of edge cases where bugs may appear.
I've thought about the de-facto standard way a lot and I think that it does nothing to avoid bugs while potentially misleading a coder about the language. Therefore I think it's worse.
The only reason I follow the de-facto standard is because the time spent arguing about it with my peers is better spent getting work done.