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…
Google C++ style guide
21–30 of 55 posts
Re: Google C++ style guide
#22I 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.
Re: Google C++ style guide
#23I 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.
Re: Google C++ style guide
#24Why 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
#25The 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.
Re: Google C++ style guide
#26I 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.
Re: Google C++ style guide
#27Earlier 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.
Re: Google C++ style guide
#28Re: Google C++ style guide
#29Earlier 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…
Re: Google C++ style guide
#30It 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.