The ever-quotable Sean McGrath penned another of his trademark aphorisms this week: “The library IS the language.” By “library” he means the great edifices of reusable code that are, in their modern form, delivered as the core Java and .Net class libraries. Mastering them is a challenge that can take years, McGrath wrote. Mastering programming languages, he suggested, is comparatively trivial.
Combining the two languages is a useful strategy as clients and servers become more equal partners. But it’s a challenge to keep track of the subtleties of these languages, and an even bigger challenge to corral each into its own mental compartment.
This interwoven use is complicated by the fact that each language has its own virtual machine and its own libraries. That isn’t necessarily a given. For example, both of these languages have been implemented on the .Net Common Language Runtime. Andrew Clinick led Microsoft’s development of JScript .Net (back when that was a live project). Jim Hugunin leads Microsoft’s development of IronPython now. Clearly it’s possible for both languages to share common .Net -- or indeed Mono -- services.
Such an arrangement would make some things a lot easier, especially if the shared engine were ubiquitously deployed both server-side and client-side. At the end of the day I don’t care whose string, XML, database, communication, and graphics libraries are the sexiest. I want to learn one set of them that I can count on to be virtually everywhere and that I can rely on to do most of what I need.
Today the ratio of languages and libraries is still roughly 1-to-1. But the numerator will grow faster than the denominator. We don’t need more of the same old ways to say the same old things, but we do need new ways to say new things.