Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Why c++ sucks dick

Name: Anonymous 2009-03-11 4:30

1) shitty compilers, shitty error messages.
-Try writing a program to insert a random character anywhere in a code file of 100 lines and see how long it takes you to track it down.  Super bonus points if the code file uses templates or is a template.  Fucking ridiculous.

2) shitty run time error messages.
-So you finally manage to fix your syntax errors, that must be the worse of it right? HAHAHAHA, good one.  You try running your program, it crashes.  No error message, no segmentation fault, nothing.  Any respectable language would tell you exactly what was wrong along with a line number and a stack trace right then and there, also handled in run time if need be(perhaps submitted as a bug report?).  In a c program, you have to compile it and run it again in debug mode.  Then maybe, if your lucky, you get a line number or a core dump.  If you are really lucky, the line number is in your file, and if you have a respectable IDE, like visual c++, you can mouse over the variables, etc.  Debugging c++ sucks ridiculous miles of dick compared to respectable languages.

3)Has terrible support for basic features
-Take for example one of the simplest data structures, a multi-dimensional array.  It has a million different uses, and yet god forbid you want to use one in c++.  You are almost always better off in c++ allocating a single dimensional array and then indexing into it like[row*rowlength+column] that, which becomes annoying as fuck when you have to type it over and over again, especially for higher dimensions. Fucking despicable.

4)Ridiculously slow compile times, even for unoptimized code.
-I'm sorry, there is just no excuse for this, whoever wrote the code for the compilers must have been fucking retarded, god fucking dam.

God Fucking Damn.

Name: Anonymous 2009-03-13 9:32

Why does C++ even exist? Why does MS keeps maintaining such a language that caused so many buffer overflows, and generally was not as secure as C# or Vb.NET.
 
 The only + point for C++ is that it compiles into machine code directly, and if we can get C# to do that, then there is no need for a language like C++.
 
 I was wondering why C++ still exists when C# is that good of a language.
 
 
 MS, why not retire C++, and just focus on C# and Vb.NET and F#?
 
 Expand C# capabilities, and get rid of P/invoke and replace it with a new kind of mechanism to call dlls outside the .NET framework.
 
 Finally, make the .NET framework really .NET, in the sense that it is distributed in terms of processing power, by enabling sharing. So that my application could use the processor that is Idle in a second room in the the house, automatically through the use of Remoting in LAN.
 
 Kill C++, and lets all be on one page, with C#.
 
 Its confusing many people, and things needs to be simpler, with few languages. C# for experts, VB.NET for beginners and intermediates.
 
 That is all.
 
 PS: some might say, there are programmers outthere who enjoy dealing with buffer overflows, and the pains of C++, and to them I say stick with Visual Studio 6 C++ IDE. and that is that.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List