Linked by Thom Holwerda on Mon 3rd Sep 2012 20:46 UTC, submitted by MOS6510
General Development I like this one: "By definition, a program is an entity that is run by the computer. It talks directly to the CPU and the OS. Code that does not talk directly to the CPU and the OS, but is instead run by some other program that does talk directly to the CPU and the OS, is not a program; it's a script." Here's the other eleven.
Permalink for comment 533867
To read all comments associated with this story, please click here.
RE[6]: C++
by kwan_e on Tue 4th Sep 2012 23:35 UTC in reply to "RE[5]: C++"
kwan_e
Member since:
2007-02-18

"I fail to see why this is a problem. The multi-style nature of C++ is better than trying to cram every problem into an OO or functional or message passing style.


I think I already expressed this from a perspective of a person that has to hire developers to develop and maintain a codebase.
When you are a lone star programmer - C++ is great.
When you have to work with a large group of people - then it becomes a problem.
"

And that's the fault of the language is it?

And no, there are not two ways of doing things in C++, there are thousands. In short - too many to be good for assembling and maintaining a team.


As another person pointed out, there is a large overlap between C++ and C. So in practice, most people actually do have similar ideas about C++.

You're confusing design with code. Programmers will always have different ideas about what DESIGN to use, whatever language it's implemented in.

Compared to languages like Python and Lisp and Java, C++ is no worse off in the different language facilities that people think of using.

Reply Parent Score: 2