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 19:15

>>62
*YOU* are full of bullshit.
 
 C++ is a horrible language. It's made more horrible by the fact that a lot
 of substandard programmers use it, to the point where it's much much
 easier to generate total and utter crap with it. Quite frankly, even if
 the choice of C were to do *nothing* but keep the C++ programmers out,
 that in itself would be a huge reason to use C.
 
 In other words: the choice of C is the only sane choice. I know Miles
 Bader jokingly said "to piss you off", but it's actually true. I've come
 to the conclusion that any programmer that would prefer the project to be
 in C++ over C is likely a programmer that I really *would* prefer to piss
 off, so that he doesn't come and screw up any project I'm involved with.
 
 C++ leads to really really bad design choices. You invariably start using
 the "nice" library features of the language like STL and Boost and other
 total and utter crap, that may "help" you program, but causes:
 
  - infinite amounts of pain when they don't work (and anybody who tells me
    that STL and especially Boost are stable and portable is just so full
    of BS that it's not even funny)
 
  - inefficient abstracted programming models where two years down the road
    you notice that some abstraction wasn't very efficient, but now all
    your code depends on all the nice object models around it, and you
    cannot fix it without rewriting your app.
 
 In other words, the only way to do good, efficient, and system-level and
 portable C++ ends up to limit yourself to all the things that are
 basically available in C. And limiting your project to C means that people
 don't screw that up, and also means that you get a lot of programmers that
 do actually understand low-level issues and don't screw things up with any
 idiotic "object model" crap.
 
 So I'm sorry, but for something like git, where efficiency was a primary
 objective, the "advantages" of C++ is just a huge mistake. The fact that
 we also piss off people who cannot see that is just a big additional
 advantage.
 
 If you want a VCS that is written in C++, go play with Monotone. Really.
 They use a "real database". They use "nice object-oriented libraries".
 They use "nice C++ abstractions". And quite frankly, as a result of all
 these design decisions that sound so appealing to some CS people, the end
 result is a horrible and unmaintainable mess.
 
 But I'm sure you'd like it more than git.

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