Which is one valid viewpoint. But he couches it in the socratic method against a strawman (presumably himself) which ultimately leaves the reader feeling dirty.
So if someone were saying to me "stop developing new languages and environments; it makes things hard", it'd be like saying "stop developing new culture or human relationships, because life is easier when we're all bland and homogenous." I find it a little bit offensive and at least a failure to recognize the important problems (due to obsession over the easy ones.)
So, to simplify, I think the reason a lot of developers roll their eyes at another new language is because the problems the languages are solving are less important than the fracturing they make in the engineering community.
If you think a language is missing something, why not contribute to the language with an RFC. C++, Java, and PHP have all been advancing significantly over the years. Or why don't you get together with 100 other language-makers and come up with a unified solution?
The problem is still in understanding what the words mean. It's easier if you have standard languages that everyone speaks, but if you want to have computers do amazing things, they'll have to be able to handle that problem, regardless of how many languages exist.
And it would be wonderful if computers could learn to understand languages regardless of who designed them and why. That problem isn't going to be solved by running away from it.