Live data from Hacker News

Monorail.js - Ultra lightweight MVC Framework for Node.js

github.com

21–26 of 26 posts

Re: Monorail.js - Ultra lightweight MVC Framework for Node.js

#21
post #4

Just wanted to ask: is there any kind of micro-frameworks for Node out there? Something comparable to Flask(for Python) or Sinatra(for Ruby)?

There's a list here: https://github.com/joyent/node/wiki/modules#wiki-web-framewo...

I've also found Grasshopper to be a great one: https://github.com/tuxychandru/grasshopper

Re: Monorail.js - Ultra lightweight MVC Framework for Node.js

#22
post #19

Earlier quoted context omitted.

As far as I can tell, this actually uses express.

Ah, I stand corrected. I apologize. I think if I were to use a node MVC framework built on express, I'd go with Matador: http://obvious.github.com/matador/

Matador actually looks pretty sweet.

Re: Monorail.js - Ultra lightweight MVC Framework for Node.js

#23
post #5
post #4

Just wanted to ask: is there any kind of micro-frameworks for Node out there? Something comparable to Flask(for Python) or Sinatra(for Ruby)?

There's Express: http://expressjs.com/ or https://github.com/visionmedia/express

Express is really nice. I was surprisingly productive almost immediately after I started using it, and enjoyed it throughout.

Re: Monorail.js - Ultra lightweight MVC Framework for Node.js

#24
post #4

Just wanted to ask: is there any kind of micro-frameworks for Node out there? Something comparable to Flask(for Python) or Sinatra(for Ruby)?

If you prefer a synchronous style (using fibers), I ported Stick from RingoJS: https://github.com/olegp/stick

Re: Monorail.js - Ultra lightweight MVC Framework for Node.js

#25

Hmm, picking the name of another MVC framework for your framework isn't great. http://www.castleproject.org/monorail/

http://en.wikipedia.org/wiki/Go!_(programming_language)

It's always strange when you see programmers who don't understand why namespace collisions are bad.

Re: Monorail.js - Ultra lightweight MVC Framework for Node.js

#26
post #25

Earlier quoted context omitted.

http://en.wikipedia.org/wiki/Go!_(programming_language)

It's always strange when you see programmers who don't understand why namespace collisions are bad.

The annoying part about it is that it's easier than ever to do a search to see if there will be a collision.
Post reply on HN