μMVC is an experiment. It doesn't provide an ORM or even a way to, say, use PostgreSQL.
It is only natural for a software system to die. Even the most needed, well designed and generously implemented systems become obsolete at some point (Norton Commander). Or they become bloated with complexity of unneeded components and/or requirements (Oracle). Or they starve to death from being so perfect that any development done on them would be nearing sacrilege (Perl). Or the worst death imaginable: getting stuck when keeping backward compatibility overweights actual development (GCC). Then again, sometimes it so happens that in a burst of uncontrolled development system outgrows its designed model into the wild unknown (Moodle, TYPO3).
Giving birth to a system, developer has to accept that sooner or later it will die.
Attracted to this similitude between the living and software systems, I (hereby) conceive MuMVC, as an experimental organic framework. I (will try to) keep its call stack low, feed it high-fiber, thought out sentences and while keeping entropy at bay I won't overdesign it either. I hope it has a prosperous life and a glorious death within the terms of experiment.
Features that won't be missed.
Please see team page.