I agree with him in principle although I agree with a lot of the other counterpoints made here too.<p>The biggest reason that other features get added to languages to make them ubiquitous is because in MANY cases companies marry their infrastructure to a particular language. With that infrastructure commitment you end up with an investment into doing everything with that particular language so if you have a feature or methodology in another language that would be good for a particular use case, your existing investments prevent you from being able to EASILY introduce a new language just for that feature.<p>Microservice architecture goes a lot way toward countering those investments. Heroku actually does a great job of removing language specific infrastructure investments from your process that make it easier to introduce language-per-purpose approaches.<p>Wrote a bit article on it for Codeship a couple of months ago.  <a href="http:&#x2F;&#x2F;blog.codeship.com&#x2F;exploring-microservices-architecture-on-heroku&#x2F;" rel="nofollow">http:&#x2F;&#x2F;blog.codeship.com&#x2F;exploring-microservices-architectur...</a>