Getting To Know NodeJS

[Ramse]

NodeJS is a server side framework, very popular these day.
Here's an interesting infographics, that guides you to NodeJS:

Do you use NodeJS, what do you think about it?

 

[TheLoneSynchro]

The only thing I don't like about NodeJS is that I don't like JavaScript. Mainly because I enjoy programming languages that don't have dynamic variables such as Java. I find sending JavaScript Objects over the network to be a waste of bandwidth (Sending everything as a String). For example, sending an Integer over the network would require the following, at a bare minimum:

{ "name": "12364327" }

Let's say that we're using the 1bpc (1 Byte Per Character) assumption here, that's 22bytes being sent over the network, apposed to just writing an integer (binary format, 4 bytes) over a network.

I've yet to see any libraries that handle binary encoding for JavaScript, which is my only complaint about NodeJS. It's a bandwidth hog under heavy loads.

Performs extremely well though.

 

[Ramse]

You do have a point there. Thanks for sharing your thoughts.

The only thing I don't like about NodeJS is that I don't like JavaScript. Mainly because I enjoy programming languages that don't have dynamic variables such as Java. I find sending JavaScript Objects over the network to be a waste of bandwidth (Sending everything as a String). For example, sending an Integer over the network would require the following, at a bare minimum:

{ "name": "12364327" }

Let's say that we're using the 1bpc (1 Byte Per Character) assumption here, that's 22bytes being sent over the network, apposed to just writing an integer (binary format, 4 bytes) over a network.

I've yet to see any libraries that handle binary encoding for JavaScript, which is my only complaint about NodeJS. It's a bandwidth hog under heavy loads.

Performs extremely well though.

 

[bretonel]

Maybe an exercise in 'perspective change' may help you:
You say you don't like js, but the language it's just a tool, what you do with it is what matters.
Would you say that you don't like a hammer?

 

[Ramse]

Maybe an exercise in 'perspective change' may help you:
You say you don't like js, but the language it's just a tool, what you do with it is what matters.
Would you say that you don't like a hammer?

Depends on what I need it for.

 

[jazzc]

I've yet to see any libraries that handle binary encoding for JavaScript

Wut?

http://bsonspec.org
https://github.com/mafintosh/protocol-buffers

 

[Ramse]

Wut?

http://bsonspec.org
https://github.com/mafintosh/protocol-buffers

Whoa! buurn

 

[deadmanwanking]

The real issue with node is that it solves the problem of parallelism, a substantial issue, by having none.

 

[jazzc]

The real issue with node is that it solves the problem of parallelism, a substantial issue, by having none.

It doesn't focus on parallelism, node isn't some MPI solution. It focuses on evented IO.

 

[deadmanwanking]

My point exactly. MPIs area also so 90s man.

 

[noon3]

I just recently started learning NodeJS (just curious about it)
what do you people use it for ? I mean alright you can make a side-server application in Node.js , but what for ? if you get me!

 

[jazzc]

I just recently started learning NodeJS (just curious about it)
what do you people use it for ? I mean alright you can make a side-server application in Node.js , but what for ? if you get me!

Streaming is a great use case. Generally, when you need to handle a lot of IO, Node is your friend. JSON API services & scraping is what I use it for most of the time.

 

[MrBlue]

Same here. It's a perfect fit for network applications.

...JSON API services & scraping is what I use it for most of the time.

 

[Ramse]

Same here. It's a perfect fit for network applications.

I'm so glad we got a nice discussion going around here.