Ask HN: Why can't we write a single system in multiple languages?

It is more common today, I think, for people to write the front end and back ends of a web system in different languages than to write them in the same language. For instance the front end might be Javascript or Typescript and the back end could be Go, Java, Rust, Python, C#, etc.<p>The same pattern can be used without the web browser by writing part of the system in one language and parts in another language and having them communicate via a &quot;web service&quot; or similar protocol.<p>Some runtime environments such as the JVM and .NET support multiple languages, so there is no problem with Clojure, Java, Jython and Scala in the same runtime or F# and VB.NET.<p>There are also methods for making calls between different languages in the same address space, particularly I would call out<p><a href="https:&#x2F;&#x2F;cffi.readthedocs.io&#x2F;en&#x2F;latest&#x2F;" rel="nofollow">https:&#x2F;&#x2F;cffi.readthedocs.io&#x2F;en&#x2F;latest&#x2F;</a><p>which is increasingly being used as a model for other languages. That one above makes it very easy to call C functions from Python. When you do this though you run into problems which are sometimes subtle and sometimes not subtle. For instance I worked on a system which combined C++ with Java and used JNI for interoperation. The worst problem I ran into was that you could not use C threads. I also ran into the problem that the gdb debugger would always be catching segmentation faults from the Java runtime because segfaults in Java are a routine condition. So it took some configuring gdb to get into a place where I could run gdb and jdb on the same process at the same time so I could debug both the Java and C++ sides of the system at the same time.<p>Note there is more to it than just having a way to share access to functions and data, you also will need answers for how you will handle dependencies, do builds, run unit tests, run an IDE, for each environment.

You mean something like this?:<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;List_of_JVM_languages" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;List_of_JVM_languages</a><p><a href="https:&#x2F;&#x2F;www.graalvm.org&#x2F;22.2&#x2F;graalvm-as-a-platform&#x2F;language-implementation-framework&#x2F;Languages&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.graalvm.org&#x2F;22.2&#x2F;graalvm-as-a-platform&#x2F;language-...</a>

Hmmm, are you a developer? Generally, language is a small part of the choice. Much comes from the ecosystem: libraries, compilers or interpreters, testing environments, CI, CD, licenses, that tend to be different. Multiply the choice and you generally multiply the cost of maintenance. That&#x27;s why the frontend and backend separation was born and why Node was actually built to try to solve. You have to maintain entire different toolchains.

Services Oriented Architecture is the most common way. Use different systems and have then communicate through HTTP or gRPC