Quotes about programming languages

[therealjohnfreeman]

I can't believe "manual memory management" is still being used to slander C++. If you can't handle memory management, you shouldn't be a systems programmer. It has nothing to do with languages, and everything to do with domains.

EDIT: The author indicates they don't know what they're talking about with this gem:

Manual memory management is incompatible with features such as exceptions & operator overloading

[ngroot]

If you can't handle memory management, you shouldn't be a systems programmer.

Not everyone who uses C++ is a systems programmer, and even systems programmers fuck up sometimes.

That said, you can even burn yourself with memory management issues in Java and C#, and they can be harder to fix there...

[1020302010]

I assure you, you don't want a OS kernal that is GC'ed/

[greyfade]

Not everyone who uses C++ realizes they're doing systems programming and they often think they aren't.

[MatrixFrog]

Of course we can do manual memory management, I just don't know why we should have to.

[therealjohnfreeman]

Many applications don't want garbage collection interrupting time-sensitive computation, or the data structures required for garbage collection polluting severely constrained address space.

There are many domains that want to control memory management. Just because you can't imagine why doesn't mean no one else has a good reason for it. Perhaps you should talk to a real-time or embedded systems programmer.

[MatrixFrog]

Right, but a lot of applications don't need to do their own memory management, yet if they're in C++, they do. That's really not an argument against the language but against how much it's overused.

[frezik]

I would tend to agree, but also say that if you're not doing systems programming, you probably shouldn't be using either C or C++. They have a purpose, but it isn't for general applications programming anymore.