OK, so now when they suspend your Google account you also get to experience loosing whatever you had in Google Drive.

Just for this I am converting my Dropbox account into one of their paid packages to do my part in ensuring they stick around.

One would hope that at one point Google might start to realize that the way they are handling accounts could work against their own interests. I --and I am sure others-- have exactly zero interest in touching any Google product other than Analytics because it can all go "poof" overnight if an algorithm doesn't like something you did somewhere...and you'll never know why and never have real recourse to attempt to fix it.

Just to be clear: I love just about everything Google has done and what they generally stand for. The one thing I hate viscerally is their approach to customer-no-service and how that relates to accounts. This aspect of what they do and how they behave is nothing less than moronic and possibly evil.

Anyone else think this is by far the most boring technical debate ever to hit HN?

I come from a Python background. However, thanks to work and school, I now program mostly in JavaScript, PHP, and Java (though I still use Python when I get a chance).

Now, I could use underscore_names in Java and JavaScript, but I don't. Even though I personally prefer underscore_names to camelCaseNames, I also realize that those languages are designed with camelCaseNames in mind, that the community conventions are for camelCaseNames, and that it is better to write code that looks nice and idiomatic in that language than it is to write code that looks nice and idiomatic in Python.

Not to mention that there are some cases where camelCaseNames are required - for example, when overriding inherited methods in Java - and if I used camelCase where required and underscore_names everywhere else, my code would be inconsistent, which to me is worse than using a style I don't like. So just because I could use underscore_names when I wanted to, there are a lot of reasons that I shouldn't.

A lot of those points also apply to JavaScript:

* JavaScript was designed with the use of semicolons in mind. Brandon Eich himself has said that ASI was only intended as an extra check for sloppy programmers.

* Outside the Ruby on Rails crowd, all the JavaScript I have ever seen uses semicolons. Even within the Rails crowd, this "no semicolons" thing is fairly recent.

* Since the majority of JavaScript syntax is intended to mimic Java syntax, which does require semicolons to separate statements, semicolons blend well with the language, and are therefore nice and idiomatic.

* There are situations where you have to use semicolons due to ambiguity to write straightforward code - there are workarounds, like tricks involving !, but they confuse the intent of the code.

One thing that I noticed is that most of the notable semicolon-haters - fat, mislav, and the GitHub guys - come from Ruby on Rails. Conveniently enough, Ruby does not require semicolons at the end of statements. I suspect this anti-semicolon fervor may come from a desire to use Ruby's conventions with JavaScript.