This is so true, but it's more than just cpu speed vs programmer speed. There are philosophies that are built in to the language and you can see them in decisio

This is so true, but it's more than just cpu speed vs programmer speed. There are philosophies that are built in to the language and you can see them in decisions made about the language, the kinds of patterns baked in, the libraries and the greater community. Say you need high reliability. Erlang has fault tolerance model & hot code reloading, it was built for telephone systems. Say you need tons of statistical features: R. Infinite Recursion: Stackless Python. Mixins Galore: _why's potion. Run a bunch of commands with little/no logic: Tcl. html generation: php. Manipulate a flash canvas: Actionscript. Manipulate html dom: javascript. Be honest, your language isn't going to stick around forever. I say make a language for a purpose with a specific problem space in mind, read papers and implement surrounding philosophies that nail down that problem well. Then it will become popular and overused to the point where it's used for things it wasn't meant for.