|
Re: Do Frameworks and APIs Limit Developers' Imagination?
|
Posted: Aug 21, 2007 1:13 PM
|
|
I think Chris Maki makes an interesting point, though I think some folks may have missed the premise. Chris starts out by contrasting his experiences as a Java developer with an earlier set of experiences on the NeXT platform (which as he points out is now -- in essence, at least -- Mac OS X). Reading between the lines, it was the NeXT platform that made the developers he worked with feel they could accomplish anything they could think of because of its rich, elegant, and powerful frameworks, not in spite of them. I don't think he was arguing against frameworks at all.
Rather, I think he was contrasting that environment with the current Java ecosystem, which features a multiplicity of frameworks that tend to be strongly prescriptive and far less flexible, channeling developers' efforts into narrow paths, and thus limiting their creativity. I've had the same experience myself, and it's been a painful thing to witness the stultifying effect this approach appears to have had on many developers.
The worst outcome of this, in my opinion, is an astonishing lack of interest in design. I'm not talking about Big Upfront Design so much as iterative design of classes, components, and layers. Most of the so-called 'architects' I've met on Java projects seem to think their job begins and ends at framework and tool selection -- they seem to think that all that's left from that point on is cookie-cutter coding that requires little to no thought.
Worse, I've worked with teams of Java developers who would rather go for root canals than have a 15 minute whiteboard session on the design of the stuff they're about to code. And I've also witnessed the resulting train wreck. Ouch!
|
|