Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Matador: MVC for Node

obvious.github.com

Post reply on HN
Print view View original

11–17 of 17 posts

Re: Matador: MVC for Node

#11

Post by chrisledet »

wavephorm wrote: post #8
chrisledet wrote: post #4

Earlier quoted context omitted.

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. ...and put it in controllers, which is terrible for large-scale organization. I would hate to see what their back-end looks like.

With that said, you obviously know little about Mustache and how to use it thus not contributing anything meaningful.

I recommend you check out Chris Wanstrath's mustache library for Ruby: https://github.com/defunkt/mustache#readme

Re: Matador: MVC for Node

#12

Post by wavephorm »

chrisledet wrote: post #11
wavephorm wrote: post #8

Earlier quoted context omitted.

It keeps code out of the views. ...and put it in controllers, which is terrible for large-scale organization. I would hate to see what their back-end looks like.

With that said, you obviously know little about Mustache and how to use it thus not contributing anything meaningful. I recommend you check out Chris Wanstrath's mustache library for Ruby: https://github.com/defunkt/mustache#readme

Yeah so instead of having a controller and a view, you have a controller and a separate formatter class which looks like this:

  module ViewHelpers
   def gravatar
    gravatar_id = Digest::MD5.hexdigest(self[:email].to_s.strip.downcase)
    gravatar_for_id(gravatar_id)
   end

   def gravatar_for_id(gid, size = 30)
    "#{gravatar_host}/avatar/#{gid}?s=#{size}"
   end

   def gravatar_host
    @ssl ? 'https://secure.gravatar.com' : 'http://www.gravatar.com'
   end
  end
I argue this will get extremely tiresome for large websites.

Re: Matador: MVC for Node

#13

Post by lukifer »

wavephorm wrote: post #2

Maybe 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'd be really interested to see how Mustache does in real world performance vs., say, PHP or Ruby templates. I'm also curious about using it to offload rendering to the browser, particularly when using Ajax or UI binding.

While Mustache sometimes seems like a solution in search of problem, I do like that it's completely logicless, and so forces all logic, even display logic, into the controller.

Re: Matador: MVC for Node

#14

Post by ryansking »

wavephorm wrote: post #12
chrisledet wrote: post #11

Earlier quoted context omitted.

With that said, you obviously know little about Mustache and how to use it thus not contributing anything meaningful. I recommend you check out Chris Wanstrath's mustache library for Ruby: https://github.com/defunkt/mustache#readme

Yeah so instead of having a controller and a view, you have a controller and a separate formatter class which looks like this: module ViewHelpers def gravatar gravatar_id = Digest::MD5.hexdigest(self[:email].to_s.strip.downcase) gravatar_for_id(gravatar_id) end def gravatar_for_id(gid, size = 30) "#{gravatar_host}/avatar/#{gid}?s=#{size}" end def gravatar_host @ssl ? 'https://secure.gravatar.com' : 'http://www.gravat…

Works pretty well for us (twitter.com).

Re: Matador: MVC for Node

#16

Post by brianjesse »

wavephorm wrote: post #2

Maybe 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 interviewed for a job @Twilio - they were using Handlebars, a Mustache variant. Also, here is my mini-chance to rant about that: I had 4 phone and 6 in-person interviews -- didn't get hired. Argh! How could anyone make it through that? Also - i'm a generalist, which seems to have kept me out of both Facebook and Twilio. /rant

Re: Matador: MVC for Node

#17

Post by tjholowaychuk »

randall wrote: post #9
geuis wrote: post #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?

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 experienc…

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
Post reply on HN