rover2341
Is riding a roller coaster...Wee!
- Reaction score
- 114
Ok So I have been hearing good things from node.js from my brothers friend. and I have kept iqnoreing him. in-till last night i decided to check it out.
(Note I may be wrong this is my impression from a day or 2 of looking at videos on sites)
What is Node.Js And what is its purpose
Purpose: "
So.. To me that means... Its able to do many things, but its goal is to have a reduced structure, and a heavily focused goal. Its also suppose to be faster. not javascrpit vs java or javascrpit vs .Net. but for non heavy cpu tasks faster to use in place of a general purpose web api.
Plus
Thoughts? Am i way off base? What do you think of Node.js http://nodejs.org/. Would you use it? Do you use it? why should/shouldn't you use it?
Edit*
The more i read on it people say... "The only purpose to Node.js is to have Javascript support as a runtime environment." so not sure if thats true. but if thats true then maybe i am way off base.
(Note I may be wrong this is my impression from a day or 2 of looking at videos on sites)
What is Node.Js And what is its purpose
- Server side Code in JavaScript
- All Functions are async
- Long Pooling (Only sends header once, keeps connection alive)
- Single Thread (No Memory Sharing)
- Free
Purpose: "
easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices."
Or in my words. scalable web api's that are async. minimum overhead and features that use long pooling.So.. To me that means... Its able to do many things, but its goal is to have a reduced structure, and a heavily focused goal. Its also suppose to be faster. not javascrpit vs java or javascrpit vs .Net. but for non heavy cpu tasks faster to use in place of a general purpose web api.
Plus
- Due to its everything async attitude, it doesn't allow anyone to lock of the program on there function by adding lets say a 10 sec wait. Its all async.
- Due to its single thread attitude, If you need to scale your program, your treating every thread like its on another computer so its design for scale is setup at the start. where it could get more complex. Not to say you couldn't do this with any other frameworks it just not forced.
- Due to long pooling, speeds up sending data and getting data. Easier to deal with large files.
- (Debate-able) Front end And Back End is in a single language so its more simple.
- (I don't have enough proof on this, likely true though) Faster then doing the same type of solution on another framework like asp.net. using single threads and long pooling.
- Free
- (I don't have enough proof on this, likely true though) Javascrpit in general is slower then other lanqaqes like Java or . Net. If you had a heavy cpu task it may become a problem, later down the road.
- No intellsense
- Debugging it is still being worked on, and not quite polished
- Its JavaScript, a lose language, in my mind less safe then java/c#.
Thoughts? Am i way off base? What do you think of Node.js http://nodejs.org/. Would you use it? Do you use it? why should/shouldn't you use it?
Edit*
The more i read on it people say... "The only purpose to Node.js is to have Javascript support as a runtime environment." so not sure if thats true. but if thats true then maybe i am way off base.