I would describe programming languages less as encoding problem domain, and more of encoding/enabling solution domains. For example, if you're in Java the langu

I would describe programming languages less as encoding problem domain, and more of encoding/enabling solution domains. For example, if you're in Java the language steers towards defining objects that have methods that express your solution, where as in Haskell you'd be more inclined to your solution in terms of a composition of functions. At a lower level, your Java program is more likely to use loops and iteration whereas your Haskell program is more likely to use a recursive solution. Anyone who's tried hammering a Java-shaped solution into an Haskell-shaped language will eventually see the folly.