Matador: MVC for Node
obvious.github.com
Matador: MVC for Node
1–10 of 17 posts
Re: Matador: MVC for Node
#2Maybe it's just me, but I honestly have trouble taking anyone who uses mustache templates seriously because I automatically assume they've never worked on a large website.
Re: Matador: MVC for Node
#3Maybe it's just me, but I honestly have trouble taking anyone who uses mustache templates seriously because I automatically assume they've never worked on a large website.
I'm the co-author of Matador. I worked on Twitter.com - which is a relatively sized website - and we used Mustache... so there's that.
Re: Matador: MVC for Node
#4Maybe it's just me, but I honestly have trouble taking anyone who uses mustache templates seriously because I automatically assume they've never worked on a large website.
From what I've read, Github uses Mustache also. Logic-less templates are nice. It keeps code out of the views.
Re: Matador: MVC for Node
#5@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?
Re: Matador: MVC for Node
#6@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?
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!
Re: Matador: MVC for Node
#7Maybe it's just me, but I honestly have trouble taking anyone who uses mustache templates seriously because I automatically assume they've never worked on a large website.
I'm the co-author of Matador. I worked on Twitter.com - which is a relatively sized website - and we used Mustache... so there's that.
Twitter has about 5 "pages" on their whole website. From a template perspective it's the MOST simple kind of website you can build. So, there's that.
Re: Matador: MVC for Node
#8Maybe it's just me, but I honestly have trouble taking anyone who uses mustache templates seriously because I automatically assume they've never worked on a large website.
From what I've read, Github uses Mustache also. Logic-less templates are nice. It keeps code out of the views.
It keeps code out of the views.
Re: Matador: MVC for Node
#9@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?
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
#10Earlier quoted context omitted.
I'm the co-author of Matador. I worked on Twitter.com - which is a relatively sized website - and we used Mustache... so there's that.
Twitter has about 5 "pages" on their whole website. From a template perspective it's the MOST simple kind of website you can build. So, there's that.
I was only counting the one page after logging in, which does everything. It's how web apps work.