Live data from Hacker News

Google C++ style guide

google-styleguide.googlecode.com

21–30 of 55 posts

Re: Google C++ style guide

#21
post #15
post #14

Earlier quoted context omitted.

Yeah, this is true. But all places pretty much require you have prior experience. Not to mention most games these days are in Obj-c/Java. Plus game studios aren't exactly ubiquitous (least not where I'm from).

> Not to mention most games these days are in Obj-c/Java. Proof? I've seen _quite_ the opposite. Sure, these things (and Flash, still) are popular among small/indie devs, but I haven't heard about a single AAA title since ~1995 that didn't used C++. There is an insane amount of big open source projects out there that use C++. Firefox, Chromium, KDE, .... the list is much longer. Making significant contributions to an…

No proof really. My last job hunt ( Nov of last year ) just came up 100% not-C++, currently doing Java work. Same thing happened a few years ago...maybe I just lived in a lame city though.

Re: Google C++ style guide

#22
post #8

I love C++, I wish there was more work available that used it. EDIT: Clearly my issue is where I lived, not the lack of available jobs apparently.

Finance /HFT. In my last job I worked for a company that sells an algo trading platform written in C++.

Re: Google C++ style guide

#23
post #8

I love C++, I wish there was more work available that used it. EDIT: Clearly my issue is where I lived, not the lack of available jobs apparently.

Still the language of choice in the world of music production software. This is not a place you'll make a lot of money but the work is far more interesting than the usual CRUD slapdash you do in most dev shops.

Re: Google C++ style guide

#24
> Functions should start with a capital letter and have a capital letter for each new word. No underscores.

Why so? It's Java-ish. Java favors camel notation for some historic reason. C++ on the other hand favors snake notation which is clearly reflected in stdc++. Snake notation is also easier to read, especially if the name contains many words in it. Of course in the end it's a matter of preference, I just wonder why Google mandates camel notation.

Re: Google C++ style guide

#25
post #10

The C++ you end up with by following Google's style guide is more of a "C with classes" thing, they prohibit several central features of C++. That said, I understand that they mostly do this to be consistent with their older code bases. But it's not exactly a style guide I'd follow strictly in a new project/team.

The Google style guide could help explain why the Go team thought that their language would make more of an impact in C++ land than it actually did.

Re: Google C++ style guide

#27

Earlier quoted context omitted.

> Code coherence can be accomplished with more relaxed rules if you delegate more responsibility to your engineers. Please elaborate.

I think consensus through code review is better as compilers and languages evolve. If you write rules for everything you spend your time checking for compliance and perhaps rewriting rules instead of relying on a more organic code quality assurance. You also want your engineers to think by themselves instead of hiding behind a rules book.

Code style doesn't dictate what your engineers build, it just makes their code easier to review and maintain. Code smells, foreign conventions, and inconsistency all make reviewing and editing code harder.

Re: Google C++ style guide

#29
post #15
post #14

Earlier quoted context omitted.

Yeah, this is true. But all places pretty much require you have prior experience. Not to mention most games these days are in Obj-c/Java. Plus game studios aren't exactly ubiquitous (least not where I'm from).

> Not to mention most games these days are in Obj-c/Java. Proof? I've seen _quite_ the opposite. Sure, these things (and Flash, still) are popular among small/indie devs, but I haven't heard about a single AAA title since ~1995 that didn't used C++. There is an insane amount of big open source projects out there that use C++. Firefox, Chromium, KDE, .... the list is much longer. Making significant contributions to an…

Speaking about remote C++ jobs - I sent an email to you more than two months ago, for the C++ dev position at Eyeo, which they still advertise on their jobs site. I sent again after a couple of weeks. No reply. Could you please confirm that this job is still active?

Re: Google C++ style guide

#30
post #4

It might sound like a good idea to precisely describe how code should be written, until you realize it's inefficient and useless. Code coherence can be accomplished with more relaxed rules if you delegate more responsibility to your engineers.

Some coding style guides amount to an obsessive compulsive disorder. They focus on trivialities, like an extra space between parameters or the placement of braces around blocks of code.
Post reply on HN