RingoJS vs NodeJS
gmosx.com
RingoJS vs NodeJS
1–10 of 39 posts
Re: RingoJS vs NodeJS
#2This was an OK piece till the last line. It's hardly a fair "vs" comparison if the aim is to call NodeJS a toy :)
Re: RingoJS vs NodeJS
#3This was an OK piece till the last line. It's hardly a fair "vs" comparison if the aim is to call NodeJS a toy :)
Don't judge the whole article by a single line...
btw, I have a special definition of toy:
6. Why not use NodeJS?
Well, NodeJS is a valid, if over hyped, solution. But it only helps you come up with a toy application. With 'toy' I mean an application that runs on your laptop or your staging server. For a production app you need deployment processes, multi version processes, system setup, server tuning, database scaling, backup processes, security policies, monitoring, profiling, admin console etc, etc. App Engine is the easiest way to go from toy to production (though Heroku-Node may provide a viable alternative).
(from http://www.gmosx.com/blog/agVnbW9zeHIPCxIHQXJ0aWNsZRipwwEM/o...)
Re: RingoJS vs NodeJS
#4This was an OK piece till the last line. It's hardly a fair "vs" comparison if the aim is to call NodeJS a toy :)
Don't judge the whole article by a single line... btw, I have a special definition of toy: 6. Why not use NodeJS? Well, NodeJS is a valid, if over hyped, solution. But it only helps you come up with a toy application. With 'toy' I mean an application that runs on your laptop or your staging server. For a production app you need deployment processes, multi version processes, system setup, server tuning, database scali…
> Don't judge the whole article by a single line...
If something is called A vs B I was would hope to see a list of how A is better than B. The only mention of NodeJS is pretty derogatory - it detracts from the promotion of RingoJS (which I found interesting)
Re: RingoJS vs NodeJS
#5Earlier quoted context omitted.
Don't judge the whole article by a single line... btw, I have a special definition of toy: 6. Why not use NodeJS? Well, NodeJS is a valid, if over hyped, solution. But it only helps you come up with a toy application. With 'toy' I mean an application that runs on your laptop or your staging server. For a production app you need deployment processes, multi version processes, system setup, server tuning, database scali…
> Don't judge the whole article by a single line... If something is called A vs B I was would hope to see a list of how A is better than B. The only mention of NodeJS is pretty derogatory - it detracts from the promotion of RingoJS (which I found interesting)
The point of the article is to bring Ringo in the spotlight. I strongly believe that the developers are doing a great job and the seamless access to Java libraries is the great selling point.
If the article generates some (well deserved) attention for Ringo, it will be a success (even if some people do not agree with the wording)
Re: RingoJS vs NodeJS
#6> ... managed to grab the attention of the developer community with cool marketing
I am not sure I would call a very good talk at jsconf "marketing" nor would I think of Ryan Dahl as "the new DHH" especially when Ryan has been known to "wish for less node.js hype".
It seems you dislike the attention node.js has been given instead of node.js itself.
> Contrast this to reports of NodeJS crashes.
This belies an assumption that node is production ready, even though it is at a very low version number, and when Ryan has stated that he would not dare put it into production standlone (not behind nginx).
Basically, I think you could have better promoted ringo.
Re: RingoJS vs NodeJS
#7> ... managed to grab the attention of the developer community with cool marketing I am not sure I would call a very good talk at jsconf "marketing" nor would I think of Ryan Dahl as "the new DHH" especially when Ryan has been known to "wish for less node.js hype". It seems you dislike the attention node.js has been given instead of node.js itself. > Contrast this to reports of NodeJS crashes. This belies an assumpti…
I don't dislike node.js (I don't agree with the direction). I just believe that RingoJS is a better solution for the majority of developers. (NodeJS may be better in niche applications like chat systems, a gaming server etc, even though I believe that technologies like GAE's forthcoming Channel API are even better)
Re: RingoJS vs NodeJS
#8This was an OK piece till the last line. It's hardly a fair "vs" comparison if the aim is to call NodeJS a toy :)
Don't judge the whole article by a single line... btw, I have a special definition of toy: 6. Why not use NodeJS? Well, NodeJS is a valid, if over hyped, solution. But it only helps you come up with a toy application. With 'toy' I mean an application that runs on your laptop or your staging server. For a production app you need deployment processes, multi version processes, system setup, server tuning, database scali…
At Plurk.com we use node.js to provide comet updates to over 300.000 active clients at _once_. It's not a toy and it scales much better than most of other web-stacks I have tried. Read more here: http://amix.dk/blog/post/19490#Plurk-Instant-conversations-u...
Re: RingoJS vs NodeJS
#9Earlier quoted context omitted.
Don't judge the whole article by a single line... btw, I have a special definition of toy: 6. Why not use NodeJS? Well, NodeJS is a valid, if over hyped, solution. But it only helps you come up with a toy application. With 'toy' I mean an application that runs on your laptop or your staging server. For a production app you need deployment processes, multi version processes, system setup, server tuning, database scali…
At Plurk.com we use node.js to provide comet updates to over 300.000 active clients at _once_. It's not a toy and it scales much better than most of other web-stacks I have tried. Read more here: http://amix.dk/blog/post/19490#Plurk-Instant-conversations-u...
comet updates are a niche application
Re: RingoJS vs NodeJS
#10Earlier quoted context omitted.
Don't judge the whole article by a single line... btw, I have a special definition of toy: 6. Why not use NodeJS? Well, NodeJS is a valid, if over hyped, solution. But it only helps you come up with a toy application. With 'toy' I mean an application that runs on your laptop or your staging server. For a production app you need deployment processes, multi version processes, system setup, server tuning, database scali…
> Don't judge the whole article by a single line... If something is called A vs B I was would hope to see a list of how A is better than B. The only mention of NodeJS is pretty derogatory - it detracts from the promotion of RingoJS (which I found interesting)
clearly points out several advantages, so i think it qualifies as comparison.
* commonjs conformant
* mature & stable
* java access
* ...