RailwayJS
railwayjs.com
RailwayJS
1–10 of 50 posts
Re: RailwayJS
#2Nicely done. Appreciate the beautiful and detailed documentation.
Re: RailwayJS
#3Wow! Mind = Blown! Thanks for doing this and giving it away for free.
Re: RailwayJS
#4Nice work. Will increase adoption of nodejs within Rails community a lot more. Bookmarked, I would give this a spin coming weekend.
Re: RailwayJS
#5Neat project! To echo what everyone else is saying, thanks for putting this out there.
I am curious as to what most HNers think of doing server side development in JS. It's obviously the flavor of the month, but I have yet to see the appeal. JS is certainly not a bad language, but it seems a lot more tedious than, say, ruby. The nesting of callbacks, the lack of built in OO infrastructure (given that most of us are trained with class based inheritance), the many quirks associated with making the language accessible to nonprogrammers. Am I missing something? Is there a really good reason to use JS on the server?
Re: RailwayJS
#6This seems very similar to Rails in structure and features, with the obvious upsides and downsides of Javascript and Node brought along. For me, the first Node framework to really catch my eye was Meteor. The live-updating, hot-code-pushing features seemed to really take advantage of the speed of V8, but I was put off by the total lack of MVC structure and other niceties of Rails (that are in Railway).
I'm still on the fence with Node and have yet to give it a real try. I think what will finally get me to jump in is something between the two. The sensibilities and structure of Rails with the great realtime features in Meteor. Just sayin.
EDIT: This does look fantastic by the way, a great contribution to the community.
Re: RailwayJS
#7Neat project! To echo what everyone else is saying, thanks for putting this out there. I am curious as to what most HNers think of doing server side development in JS. It's obviously the flavor of the month, but I have yet to see the appeal. JS is certainly not a bad language, but it seems a lot more tedious than, say, ruby. The nesting of callbacks, the lack of built in OO infrastructure (given that most of us are t…
Nested callbacks naturally allows for non-blocking code, which leads to higher request capacity.
In, say, Ruby, you've got EventMachine for something equivalent but it's definitely "bolted" on to the language. Python has Twisted, with which I have no personal experience. In PHP, there are really no options.
Re: RailwayJS
#8Neat project! To echo what everyone else is saying, thanks for putting this out there. I am curious as to what most HNers think of doing server side development in JS. It's obviously the flavor of the month, but I have yet to see the appeal. JS is certainly not a bad language, but it seems a lot more tedious than, say, ruby. The nesting of callbacks, the lack of built in OO infrastructure (given that most of us are t…
The main reason Node.js is gaining popularity is because it is blazing fast, scales very well due to its IO + event driven architecture and it has the best support for websockets (see socket.io).
On the flip side, code can be hard to maintain and you need to be more disciplined so that you can read the code later otherwise it becomes a callback spaghetti. Doing everything through callbacks also requires a mental shift.
Like with everything in life, there are pros and cons and tradeoffs. So choose wisely :).
Re: RailwayJS
#9Neat project! To echo what everyone else is saying, thanks for putting this out there. I am curious as to what most HNers think of doing server side development in JS. It's obviously the flavor of the month, but I have yet to see the appeal. JS is certainly not a bad language, but it seems a lot more tedious than, say, ruby. The nesting of callbacks, the lack of built in OO infrastructure (given that most of us are t…
Nested callbacks in JS means functions are first class members of the language..
...
thus
...
Functional programming is possible in JS..
...
thus
...
You can create beautiful abstractions with your code.
Re: RailwayJS
#10Neat project! To echo what everyone else is saying, thanks for putting this out there. I am curious as to what most HNers think of doing server side development in JS. It's obviously the flavor of the month, but I have yet to see the appeal. JS is certainly not a bad language, but it seems a lot more tedious than, say, ruby. The nesting of callbacks, the lack of built in OO infrastructure (given that most of us are t…
The main reason Node.js is gaining popularity is because it is blazing fast, scales very well due to its IO + event driven architecture and it has the best support for websockets (see socket.io). On the flip side, code can be hard to maintain and you need to be more disciplined so that you can read the code later otherwise it becomes a callback spaghetti. Doing everything through callbacks also requires a mental shif…
I'm sorry I don't buy JS code is hard to maintain analogy.
If you write modular and/or functional code, JS code bases can be just as easy / hard to maintain as any other language.