25 comments

[ 3.0 ms ] story [ 63.8 ms ] thread
How is that light weight? let's see it has scripts for skeloton projects/models/etc, has it's own orm's, and even ships with its own package manager. that seems like a lot of stuff is you're looking to light weight.
(comment deleted)
Wow, what a hostile response.
I think he meant

    [ u s e r @ma c h i n e E x amp l e ] $ . . / mo n o r a i l . j s i n s t a l l mo o t o o l s
The M in MVC has nothing to do with database persistence. That is a wonderful perception that rails and its ilk have given us, for better or worse. You could build a complete system that fully implements MVC without database persistence, or really any persistence at all.
"How is that light weight?"

Look at the description:

"Monorail.js will never force you to install anything not needed for your project. The goal is to use what you need."

Plus, it's definitely lighter than express.

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)?
I've been using Backbone.js for MV'C' in Node.js and re-using my models on the client side.
Backbone actually looks pretty good.
Also, Geddy might be just as good if not better than backbone.
Hmm, picking the name of another MVC framework for your framework isn't great.

http://www.castleproject.org/monorail/

A few years ago you couldn't search for Go examples because it was seen as a common word instead of a query. Same thing happened to C# at first.
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.