for(vector<some_really_complex_type>::iterator itr = something.begin(); itr != something.end(); ++itr)
Then you need to use "itr." It's a pointer-like thing that isn't quite a pointer, and when you hold pointers in your container, which you often (usually) want to do you have to deal with a pointer-to-a-pointer which is almost never pleasant. And when you deal with keyed containers you have to remember the iterator actually points to a pair so you have to do .first and .second (why not .key and .value?)Braindamage doesn't even begin to describe it.
The containers have been designed with this is mind.
If you don't use the algorithms, indeed, the STL can be cumbersome to use.
See std::for_each, std::transform, std::accumulate, std::partition, etc., etc.
First of all, like you've mentioned, his C++ example code is bogus. Second of all he says "modern funkiness of dynamic languages" only to continue with lambda, map/reduce and type independence. The first two are unrelated to dynamic/static typing, the latter is incorrect or badly phrased. You don't get "type independence" in dynamic typed languages, the types are still there. Thirdly, he greatly exagerates the complexity of templates (thousands of incorrect syntax options for smart pointers, all you have is a hammer, etc)
It's a classic case of fishing for arguments to support an idea.
It is available in compilers today -- for example, Visual C++ 2010 supports "auto".
The problem is that when you notice something inaccurate in a document, you have the tendency to ignore the rest...
It is a superior alternative for classic application development, and some nice slim and full-featured GUI toolkits use its qualities well.
I would say C++ is the way to go for servers, not really GUI. As much as I love C++ I wouldn't recommend using it for writing a GUI.
dynamic_cast<MyData>(funky_iterator<MyData &const>(foo::iterator_type<MyData>(obj))
I get it's a joke, but it would be a better joke if it was actually valid C++ or close to something you would actually write.
contemporary C++ using STL looks like a classic case of the "If all you have is a hammer"-syndrome
I don't understand what it means. The STL is a very powerful tool to implement complex data processing and work on structure. Is this another case of someone using the containers without using the algorithm's functions?