5 ms·

I wish more people would read this blog post before writing another MVC framework in Node. http://eflorenzano.com/blog/2010/09/27/why-node-disappoints-me/ http

I wish more people would read this blog post before writing another MVC framework in Node. http://eflorenzano.com/blog/2010/09/27/why-node-disappoints-me/ http://eflorenzano.com/blog/2010/09/27/why-node-disappoints-...

No1 14y ago
It looks like Sail.js is a pretty good response to that blog post. It doesn't go all the way of his dream framework, but it also isn't just another straight "Sinatra/Django/Rails" clone.
gregr401 14y ago
Except without leveraging those V8 features, we don't have what makes node. The pace of invention today is based on iteration, building upon other successes and similar ideas - and its happening in real-time across a vast community. This is awesome. Personally, I love that we have choices like derby, meteor and potentially, sail. Every effort has pro's / con's that may or may not be ideal for a particular use case. I would rather have more options than none.
- tracker1 14y ago
  I think my issues with this are that it's cool, but there's no example of security, and the tests are pretty much missing... I tend to look for either tests, or samples for how things get done, and without any security/authentication bits, I don't know what I would use something like this for.
deleted 14y ago
[deleted]
api 14y ago
TFA says "You know what would be awesome? If we wrote our libraries so that they could run either on the server or on the client, and they did so in a transparent way." Ever tried GWT? I played with it a bit. It gives you One Language -- Java -- and does a pretty good job of it. It comes the closest to accomplishing what the author is talking about. Unfortunately it puts this huge condom between you and the web medium itself, making design nuance difficult to achieve. But if I had to write, say, an accounting app for a car rental agency I would seriously look at it. It would be a great way to create a solid, stable web thin client app.

No1 14y ago

It looks like Sail.js is a pretty good response to that blog post. It doesn't go all the way of his dream framework, but it also isn't just another straight "Sinatra/Django/Rails" clone.

gregr401 14y ago

Except without leveraging those V8 features, we don't have what makes node. The pace of invention today is based on iteration, building upon other successes and similar ideas - and its happening in real-time across a vast community. This is awesome. Personally, I love that we have choices like derby, meteor and potentially, sail. Every effort has pro's / con's that may or may not be ideal for a particular use case. I would rather have more options than none.

tracker1 14y ago
I think my issues with this are that it's cool, but there's no example of security, and the tests are pretty much missing... I tend to look for either tests, or samples for how things get done, and without any security/authentication bits, I don't know what I would use something like this for.

deleted 14y ago

[deleted]

api 14y ago

TFA says "You know what would be awesome? If we wrote our libraries so that they could run either on the server or on the client, and they did so in a transparent way." Ever tried GWT? I played with it a bit. It gives you One Language -- Java -- and does a pretty good job of it. It comes the closest to accomplishing what the author is talking about. Unfortunately it puts this huge condom between you and the web medium itself, making design nuance difficult to achieve. But if I had to write, say, an accounting app for a car rental agency I would seriously look at it. It would be a great way to create a solid, stable web thin client app.