We had exactly that situation for many years. We'd write our server software in C or C++, and we'd write our client software in C or C++.
A bit later on, and we saw Java become popular. Soon we were writing server-side code in Java, and accessing these servers using client apps written in Java.
Some time after that, we saw people and organizations more in the Microsoft camp doing the same with VB.NET and C#.
It's only with the relatively recent rise of web apps, and the inflexibility brought on by JavaScript being the only viable scripting language supported by the major browsers, that we've seen this issue arise.
Having to use JavaScript on both the client-side and server-side shouldn't be seen as beneficial in any way. It's actually just a very negative side effect of JavaScript being the only option for client-side web development.
So this shouldn't be seen as something negative: it's great, actually, that javascript is evolving in this way. It will allow for more flexibility: you can write your server software in clojurescript, your client software in coffeescript, and still share some common libraries for functions you need to call on both client and server.
But why complicate things with multiple languages if you can use one? Then all developers can understand and edit the codebase.