Here's a nice post on choosing dynamic languages that some of the enterprisey architect types ought to read:

"We have a wonderful ability here to choose the right tool for the job. We have components that are written in Java, in C++, in Python, and Ruby and Perl. [Python is] definitely viewed internally here by some of the best computer scientists in the world, people from MIT's AI [artificial intelligence] and CS [computer science] labs, as enterprise worthy," he said.

The summary from Bill Barr is also worth pondering:

There is also a great quote about line-coders vs. problem solvers, but I'll leave it up to readers to find that gem. I also have to add that from personal experience, it's a whole lot easier to teach a bunch of mainframe and COBOL programmers Python than it is Java or C#. In fact, it was really just a matter of pointing them in the direction of Python, asking them to use pyUnit and let them run wild. On the other hand, teaching them Java drained tens of thousands of dollars from my operating budget!

Swap Smalltalk in for Python, and it's the same thing - I'll toot my own horn a bit and point beginners to my screencast series as a good place to get started.

Technorati Tags: dynamic, enterprisey