> But as I write, we need lots, not one or two. And those connectors need to be pushed down into the subsystems. This is the problem. Whatever the language u

> But as I write, we need lots, not one or two. And those connectors need to be pushed down into the subsystems. This is the problem. Whatever the language used, you've effectively described a shared library, and one that needs to be handled by external cooperating services (including data stores). > For good reason, because the reverse case is fine. It is not, as per my above comment. Consistency requires bi-directional participation between actors if done at a uniform language or interface level, and good luck getting MySQL or Postgres to push your semantics into their software. For any HN users who are reading this and think "hey, writing everything in one language is totally fine!" please consider the first day you acquire a company / are looking to be acquired by another company that didn't use your language.