Hmm. Thanks for that info, p. sim.
One of the things I'm adamount about with a framework solution is that:
a. It allows me to maintain my own URL format., ie, I can use domain.com/apples/oranges or domain.com/blog/this-is-an-article/comments rather than it forcing functionality into the url like domain.com/files/functions.cfm?do=that. I mean, it's one thing if I can call functionality in the framework with an AJAX or other "behind the scenes" HTTP request, that's fine. But when it comes to the user seeing the URL in the address bar, I want that to be all me.
b. It allows me to have my own directory structure for where I put files. Though I understand that MVC in its very nature is about separation of logic, presentation and data (and I'm fine with that), it would need to support my naming structures for the application's directories.
I've heard about Fusebox the most, and in the few CF job postings I've seen, when they mention framework familiarity, they usually list Fusebox as the preference. I do like your line on spending time on what to build than how to build.
Can you recommend a good place to learn Fusebox? Their website seems to suffer from what I call "Developer-itis", where it's not necessarily being presented in an easy to consume manner (though I understand that's a subjective statement). Fusebox seems like something well worth learning since it can optimize my build process.