Fair enough (and the last point certainly is true). My use of "dynamic languages" was a lazy way of referring to several less strict, highly expressive languages. I used it in the sense that Yegge used it in his talk that I link to. While writing it, I had Ruby, Python, and Smalltalk in mind.
I should point out that my lack of consideration of Java was more due to my perception of it being C++ (a language that I have written far too much of) without all the fun or peril.
You are entirely correct that it isn't the type system that makes a language, but it does provide a convenient if highly inaccurate way to speak broadly about a set of languages.
Comments
Fair enough (and the last point certainly is true). My use of "dynamic languages" was a lazy way of referring to several less strict, highly expressive languages. I used it in the sense that Yegge used it in his talk that I link to. While writing it, I had Ruby, Python, and Smalltalk in mind.
I should point out that my lack of consideration of Java was more due to my perception of it being C++ (a language that I have written far too much of) without all the fun or peril.
You are entirely correct that it isn't the type system that makes a language, but it does provide a convenient if highly inaccurate way to speak broadly about a set of languages.