I'm developing my own framework and began noticing something odd. There seems to be this trade off in complexity in designing a good framework vs creating massive numbers of files along with a touch of copy-n-paste that makes for agile programming. I think many of us would prefer just "getting something out there" by avoiding the stereotypical configuration hell, along with understanding all of a framework's idiosynchrasies. The thing that sucks with these frameworks is the sheer number of files one must work with as opposed to redoing a unit of work each time. I have to admit that even the framework I'm working on is starting to get hairy. It's like you're trying to manage complexity by building more complexity and dependencies into these things. One slip of a file and you're lost. Compare that to a single file that looks more like a scripting mess, but which may turn out to be easier to change since everything is centralized.
I guess one thing in the end to realize is what you expect from such exercises. I'm still debating whether or not one side is right. I think in the end though I would like to lean towards the side that eliminates complexity. Don't you agree?
Sphere: Related Content
Trackbacks: (Trackback URL)
