Isn't this typical of what you get when you have a language that's easy for newcomers to pick up? At one point it was PHP. Then it was Rails. Of late it's been

Isn't this typical of what you get when you have a language that's easy for newcomers to pick up? At one point it was PHP. Then it was Rails. Of late it's been Node. I'm sure Windows users might have some old VB war stories. (Admittedly, I'm not sure what to make of the Java StackOverflow tag, seeing that it's also is a sewers. Presumably school or Android related.) Edit: good related reading: http://yosefk.com/blog/redundancy-vs-dependencies-which-is-worse.html http://yosefk.com/blog/redundancy-vs-dependencies-which-is-w... > Redundancy sucks. Redundancy always means duplicated efforts, and sometimes interoperability problems. But dependencies are worse. The only reasonable thing to depend on is a full-fledged, real module, not an amorphous bunch of code. You can usually look at a problem and guess quite well if its solution has good chances to become a real module, with a real owner, with a stable interface making all its users happy enough. If these chances are low, pick redundancy. And estimate those chances conservatively, too. Redundancy is bad, but dependencies can actually paralyze you. I say – kill dependencies first.