Honestly the "[dynamically typed scripting language] is much more productive than [statically typed compiled language]" arguments sound like bullshit. There's

Honestly the "[dynamically typed scripting language] is much more productive than [statically typed compiled language]" arguments sound like bullshit. There's just too many things to take into account: - the developer's experience with a particular language - the developer's experience with the problem domain / understanding of the task / etc. - time spent writing the code but also time spent debugging it - time spent debugging a few weeks later when it suddenly breaks in production (dynamic typing often fails there) Really, the most productive language is the one you're most familiar with. I still use Python and Ruby for various tasks (mostly for scripting, command-line apps, simple services). Their main advantages are their library ecosystems and portability* . But they aren't very good for serious app development. Even when you feel like your business logic is extremely simple, you WILL get that weird null (sorry, None) or completely unexpected exception in production. * I mean, you can easily run a Python script on, say, an iBook G4 running OpenBSD/macppc, or an old ReadyNAS with Debian/SPARC, or your MIPS home router. I like obscure hardware :)