3 ms·
A problem is that a lot of developers equate MVC with magical framework that does a lot for me and just happens to have folders named "models", "views", and "co
by bdcravens 13y ago
A problem is that a lot of developers equate MVC with magical framework that does a lot for me and just happens to have folders named "models", "views", and "controllers" where they put stuff. This can be Rails, but is common in other frameworks as well (even if the names change)
I found working with a barebones MVC framework a bit enlightening. One is Framework One by Sean Corfield. It was originally written in ColdFusion, consisting of a single class (CF calls them "components") with very little magic. (it does do things like implicit views and queue up service/model calls with an event lifecycle, but in general, nothing happens that you don't have direct control over) He's also written a version for Clojure, though it's less mature
https://github.com/framework-one/fw1 https://github.com/framework-one/fw1
https://github.com/framework-one/fw1-clj https://github.com/framework-one/fw1-clj