Live data from Hacker News

Ruby, Let's Take a Break. I Want To Date Node For a While.

grantmuller.com

1–10 of 32 posts

Re: Ruby, Let's Take a Break. I Want To Date Node For a While.

#2
A friend who is wrapping up the last year of his computer science education asked me last night "so what's this node.js stuff all about?". I thought about it for a few seconds and then told him the value of writing a web-app in node was the ability to use 1 language from top to bottom.

In my experience, most of the detractors of node seem to miss the value that a homogenous programming environment can bring. I'm interested to see how your courtship with node pans out over the long term; good post :)

Re: Ruby, Let's Take a Break. I Want To Date Node For a While.

#5
The problem with the internet is that people now have the ability to affect a larger amount of opinions than ever before, for better or worse.

I think node is cool, and definitely has its place. I think it's a bit premature when people start talking about it being a full stack replacement. I certainly believe under some circumstances node really shines, but you need to pick your battles using the right tool for the right job. Stay educated and understand why something works to solve a particular problem well.

Re: Ruby, Let's Take a Break. I Want To Date Node For a While.

#6
post #4
post #3

The ability to share models/code between the client side and server side is magic at first. Javascript on every level with the data encoded in JSON? Yes, please.

I keep hearing about this, but has anyone actually done this?

And furthermore, what are the security ramifications of doing this?

At first glance, it seems attackers would be able to forge JSON objects resulting in "mass-assignment" style vulnerabilities (unless there is lots of protection logic) when sending JSON objects back to the server side.

However, going in the other direction (sending JSON from server to client) is a very common pattern.

Re: Ruby, Let's Take a Break. I Want To Date Node For a While.

#7
post #4
post #3

The ability to share models/code between the client side and server side is magic at first. Javascript on every level with the data encoded in JSON? Yes, please.

I keep hearing about this, but has anyone actually done this?

BrowserQuest, which is written in Node, put their inventory tracking system client side. Brilliant!

http://www.raymondcamden.com/index.cfm/2012/3/28/How-I-cheat...

Re: Ruby, Let's Take a Break. I Want To Date Node For a While.

#8
post #2

A friend who is wrapping up the last year of his computer science education asked me last night "so what's this node.js stuff all about?". I thought about it for a few seconds and then told him the value of writing a web-app in node was the ability to use 1 language from top to bottom. In my experience, most of the detractors of node seem to miss the value that a homogenous programming environment can bring. I'm inte…

I've used node, and I just don't see it.

You can share fragments of code, but for reasons of both security and logic not much more. In my view, the evented nature of node negates most of the pluses of one language.

Additionally, javascript is a shitty language if what you want is a large amount of business logic. Python and ruby are much more concise and expressive. This is a huge win that a lot of people overlook.

Now, if you need to throw together a chat service or push service really quickly, I see the value, but that's about it. Of course for that, I'd just use clojure or java.

Re: Ruby, Let's Take a Break. I Want To Date Node For a While.

#9
post #5

The problem with the internet is that people now have the ability to affect a larger amount of opinions than ever before, for better or worse. I think node is cool, and definitely has its place. I think it's a bit premature when people start talking about it being a full stack replacement. I certainly believe under some circumstances node really shines, but you need to pick your battles using the right tool for the r…

Whoa, who said anything about full stack replacement. I use a variety of stacks, I was simply pointing out that since I'm using Javascript all over the place anyway, I might start using it on the server side as well. Things I use Ruby for generally amount to one-off jobs or shell-scripts. I constantly have to remind myself of the syntax, since all I use all day long are variants of C syntax(C#, java, javascript). It'll take me 10 minutes to whip up what would take me 30 in ruby, simply because I don't use ruby often enough to internalize the syntax. node provides me with a way to write the same shell scripts in javascript.
Post reply on HN