There's a huge problem of how to teach people good, responsible software development, and this article is a part of my attempt to help educate people towards even knowing about better software practices. People aren't going to just suddenly get it, they have to learn from somewhere.
Two awesome places to learn shit:
http://martinfowler.com/bliki/
Both of those are available as books (EIP + PoEAA). Buy them, read them, weep.
Yes they are C# and Java but that's where most of the formalisms were developed (for a reason!).
A large portion of any industry ignores established best practices and makes a mess every generation.
Yes, and many of them described in books in particular languages. Not every language community that could have benefitted had the right book written using their language.
Like I said, a recurring condition and an opportunity.
It's easy to get a lot of followers by creating a framework that lets a new user create something small very quickly. Keeping it well organized as time goes on is much harder. It has been this way for decades, and still people haven't learned.