Re:Matador: MVC for Node
by geuis on Wednesday January 04, 2012 @05:43PM
(#3426301)
@dustindiaz I'm curious about the usecase for Matador. Its mentioned in the docs that it uses Express. I use Express pretty heavily and it seems that most of the things made available via Matador is already available in Express. Why should I consider stacking Matador on top of a framework that already works pretty well?
[ Parent
| on HN ]
Re:Matador: MVC for Node
by dustindiaz on Wednesday January 04, 2012 @05:57PM
(#3426379)
Great question. And fwiw, we love Express too! After building a number of Express applications myself, I quite often ran into organizational issues (such is the loosey goosey way of Sinatra). Matador takes more of a Rails approach to organizing your code; of course, without all the extra cruft that comes with Rails.
We still tack on Express requests and responses onto your controller instances.
Most of all, the router -> controller mapping with request filtering (middleware-like) is where Matador comes in most useful. We have other features we'd like to add, especially in the scaffolding layer, but figured we'd open source early and get developer feedback.
Thanks!
TJ's goal (in my view) is to make a really unopinionated way for node to interact with the web in a modern way, standardizing things like routes, sessions, etc. Matador would provide some opinion on top of Express to standardize file locations, or do a Rails-like inference of inflection perhaps. (I haven't looked deeply).
I wrote my own version of this last year, and found that it was a really good learning experience, but I didn't think it was worth publishing publicly. However, there is definitely room for a scaffolded MVC prototyping framework on top of Express, imo.
Re:Matador: MVC for Node
by tjholowaychuk on Thursday January 05, 2012 @12:56AM
(#3427621)
yup that's certainly correct. Express is still intentionally much lower level so myself and everyone can just craft what they want without fighting some larger framework