C++ a shit.

http://www.250bpm.com/blog:4
Now, almost 5 years later, I would like to publicly admit that using C++ was a poor choice and explain why I believe it is so.

He still doesn't fully understand, but it's better than nothing.

The writer of that blog is an idiot and you are an idiot.

C++ is great

The fact that it's so Sepples-centric is the main reason I never bothered with ØMQ. I don't think a C rewrite is forthcoming, though.

>>3
sepples is fucking shit.

be too dumb for C++
criticize it
lel

>>6
use language
constantly work around shortcomings of language
Writing applications in C++ is like writing haikus in english. Sure everyone can understand you, but the result is always terrible.

>>7
It's possible to write an understandable haiku in English. You can't say the same thing about writing applications in C++.

>>5
And yet it's the industry standard for PC game development. Gee, I wonder why that is..

>>9
It's because a sepples compiler is part of Visual Studio. If MS made Visual COBOL with IntelliSense™ and MSDN used COBOL syntax for all functions and types used by DirectX and the Windows API, COBOL would be the "industry standard for PC game development."

>>9
It's because game developers are barely a step up from web developers in terms of average competence.

>>10

Then why aren't more developers switching to C#? Visual Studio supports that as well but you don't see many people utilizing it for game developers.

>>11
And then what, everyone else? There is no "hierarchy" of competence in the computer science industry. You're either good at your specialty, or you're not.

Why are the people on this board such speds?

>>11

ONE WORD. THE FORCED INTERPOLATION OF UNIT LENGTH QUATERNIONS. THREAD SMOOTHLY TRANSITIONED.

>>13

That's more than one word. Nigger.

>>12

actually, lots of people use C# for gamez. And it's for the exact reason provided in >>10

http://en.wikipedia.org/wiki/Microsoft_XNA

>>15

True, but what are the alternatives? The only decent one I can think of is Java, and maybe Python.

Other than these 2, I wouldn't give a 2nd thought for and of the shitty nix boon languages like Cobol, LISP, etc. the retards here talk about for no reason.

>>16

There's a difference between liking a language for what it is and liking a language for its level of use or amount of support.

>>17

But that's my point, java and python are viable alternatives. Shit like cobol is just oudated, underdeveloped, blahblahblah...tl;dr shit

>>18

cobol isn't bad because it is old, it's bad because it itself is shit. There are plenty of modern languages that are just as bad. And yet they might still be used for various reasons. Programming languages don't really go out of date. Hardware might, due to it being produced using technology that existed when it was produced, and technology is progressing all the time. But we haven't really gotten anywhere for programming languages. Instead we follow fads and label something new that uses a specific combination of concepts that have been around for decades. And then with enough market lock in, it might become popular and industry standard.

SEPPLES TEH ULTIMATE SAGE

Learn Lisp then reinvent it.

bampu pantsu