[sh_vipin]

"Not possible to have made in C." -- Is it really true ?? I don't need the answer. You need to answer yourself.

"one guy (or a small team), properly trained and experienced, can move mountains with a high-leverage language." -- But if guy is not properly trained he can create a mess which is hell to clean also.

"1000 monkeys on 1000 typewriters can make something large in C" -- Every time you are using an STL container, that container has already been written by someone else. Every template you use, compiler generates the actual code for it. Every time you include a library , it was written in actual C/C++ code by someone else. Use g++ -E option to compare the "pre processed" code and compare the things.

[JoeAltmaier]

Yeah - stl. That's the issue isn't it? Its a mess to use stil embedded or for OS work - so I never, ever do.

Libraries are used by app guys -rarely by OS or embedded - unless they are specific to the hardware etc.

I hear the excuse "you can hurt yourself in C++ if not trained". That's true, but not helpful. You can build a house with hand tools too but nobody does any more - they use power tools and professional carpenters, electricians etc.

[sh_vipin]

There is a saying "At times a needle can do what a sword cann't" . Same holds true in case of programming languages !!

There was no excuse. There was a point made - "If one likes C++ use C++ nobody is stopping him/her. But that doesn't mean all other languages are bad or are pathetic."

I wonder if C++ is so good and STL is such a godly thing then why did we need to go to Objective-C. Why do iOS applications need that and why didn't C++ and STL did the magic. The answer is every tool / technology has its application. Loading a heavy container ( vector/ list) doesn't make sense when all you need to implement is a skip list.