Precisely :-) ... everyone has different needs - MooTree was designed to be a lean and developer-minded, making it easy to use it as a "core" for your application-specific functionality.
Everyone has different needs - the more features you add, the more bloat everyone has to drag around, and even if it does a million things, there's still a high chance that a component doesn't do precisely what you want.
If you agree with this way of thinking, you might also want to check out my template engine for php:
It's based on the same ideas - it's a lean and very open core, providing common functionality, while attempting to leave every option open for developers to build on top of it.
In my line of work, I build to meet exact specifications for every project, and I can do this faster and more accurately, and without unnecessary bloat, when I have lean and extensible components to build upon, both on the server-side and client-side.
I have also started work on a php platform, but it's very early days for this ...
Not much code to see yet, but as you can see from our mission statement, we're aiming for a lean and extensible codebase. It's going to be a kind of framework, but we prefer the term platform, because we don't want to build yet another MVC framework, or some other fixed pattern - we're trying to leave all options open, solving common tasks in a way that doesn't try to lead you or get in your way.
I believe that every project should be approached in the way most suitable for that project - frameworks that try to be the "end-all be-all" solution for any project, quickly end up in bloatware-land, and usually lead you to use the same patterns for every solution. I prefer a more agile approach.
So now you know a little bit about where I'm coming from :-)
And of course, if mifjs meets your requirements better, use it! That's what I would do - I don't use my own tools for every solution,I use whatever solves the task at hand in the simplest, fastest and most elegant way!
- Rasmus