I posted some commentary on the same topic last time Nick Kallen's infamous "I love everything you hate about Java" blog got posted : http://news.ycombinator.com/item?id=3287777 .
What it boils down to is that Java likes invoking the names of design patterns with all sorts of pomp and ceremony (look, ma, it's an AbstractFactoryFactory!) while many more modern languages make similar design patterns natural.
Whether or not to like the ritual is up to the programmer, but I entirely agree that claiming that Ruby and Python are "just starting" or "don't" support patterns like dependency injection is absolutely baseless.
> As far as IoC containers are concerned, I don't see
> Ruby/Python communities using it, mainly because half of
> it is fighting static typing.
Exactly. Jim Weirich gave a presentation on DI 2005 http://onestepback.org/articles/depinj/index.html also see a nice writeup by the Jamis Buck—the author of a couple of DI frameworks: http://weblog.jamisbuck.org/2008/11/9/legos-play-doh-and-pro...http://weblog.jamisbuck.org/2008/11/9/legos-play-doh-and-pro...
He's calling node style callbacks spaghetti code. Which it is, and it's a known problem, and there are several half-baked solutions for it.
This remark is off the mark. Dependency injection, as in injection by parameters and injection by constructors are so obvious people do it sub-consciously. A fluff word isn't needed for it. As far as IoC containers are concerned, I don't see Ruby/Python communities using it, mainly because half of it is fighting static typing.
And people are learning proper modularization now? Seriously? Python/Ruby has proper namespaces(ruby doesn't have it), modules, classes et al. Like any other languages, Python/Ruby has it's share of programmers who write spaghetti code, and programmers who don't.
Again, if he writes AbstractConnectionDepenencyInjectioManagerAbstractFactory and calls it proper modularization, I am happy Python/Ruby isn't picking it up.