Yet he gives absolutely no justification for why those are "tomorrows languages". You don't use third party libraries or frameworks in any of those languages?

Personally I design my Django code to be as simple as possible. I use third party libraries, and don't see too many of the problems he talks about.

That's the issue: he calls them tomorrow's languages, implying that they need to change ("can you marry modern thinking, build a community [...]) before getting there, or being "today's languages".

So far, I still haven't seen anything better than Rails to solve yesterday's (and today's) problems.