|
|
|
|
|
by davelnewton
4006 days ago
|
|
While a Single Language to Rule Them All would be cool, I ultimately prefer using the "best" language for the job based on specific requirements. The "best" might change over time, too. It can be a headache to manage massively-polyglot environments. At the same time, it's also pretty great for a variety of reasons. I mean, we regularly use different data stores, messaging solutions, frameworks, etc. and I don't see why languages shouldn't also be up for shuffling. |
|
Most shops don't think like that. Using too many languages often quickly becomes unmanageable.
I wouldn't use 6 different languages into the same project UNLESS they are part of different server/cli tools that work in isolation. I don't need to have a deep understanding of Go to use Docker, I don't need to be a PHP expert to deploy Drupal or Wordpress , I don't need to know Ruby to use vagrant,nor Java to use Cassandra. So using these tools in isolation is fine inside the same project.