Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'm just curious why Node.js was named that. I searched their site and their FAQ and there was nothing that helped me understand why it was named Node.js.
The official name is actually Node. Originally it was designed for use as a web application, but the author realized it could be used for more general purposes and renamed it to node.
Here is a quote from the author that may help explain the name:
Node is a single-threaded, single-process system which enforces shared-nothing design with OS process boundaries. It has rather good libraries for networking. I believe this to be a basis for designing very large distributed programs. The “nodes” need to be organized: given a communication protocol, told how to connect to each other. In the next couple months we are working on libraries for Node that allow these networks.
Check out this article. From page 4:
Originally, Dahl called his project
web.js. It was merely a webserver, an
alternative to Apache and other
"blocking" servers. But the project
soon grew beyond his initial webserver
library, expanding into a framework
that could be used to build, well,
almost anything. So he rechristened it
node.js.
On wiki it says, that the project is called node, but to make sure it does not get mixed up with other "node", the .js was added to it
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What is a "NodeJs project"? How would you describe a node project to a person that is moving to learn nodeJs? Or, at a job interview, for example, if someone asked you this question, how would you reply? How would you describe a "node project"?
A node project is any program that is built to run on the node.js Javascript engine and use its built-in runtime library. It could be a simple one file script to carry out some sort of local scripting operation or it could be whole directory hierarchy of script files and installed modules designed to be a clustered server running a website at scale or anything in between.
node.js itself is a very flexible development environment that can be used to create a wide variety of programs. It's somewhat analogous to Python (though obviously a different language) in that it comes with a language interpreter, a runtime library of built-in functionality and a community of modules (most of which are open source) that you can add in to your project.
If you're hoping to seem node.js-proficient in an interview and don't even know the answer to this already, then you have a lot of additional studying to do because a few simple followup questions about the relevant strengths of node.js compared to other environments or a few quick programming questions about the node.js environment would likely quickly show the limitations of your knowledge.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
At the risk of this question being closed I will ask anyway.
I have been looking at the different JavaScript Frameworks as most jobs roles seem to want:
angular.js
Knockout.js
Node.js
Whilst i can see Angualr.js and Knockout.js provides a MVC construct to the markup pages (though still not sure which one is best to use) I cannot see what is the case for node.js?
Whilst I appreciate node.js is good for real-time comms but so is Signalr as they both use long-polling.
At present I use signalr to update images on my clients.
is there any purpose to swapping this out for node.js?
Like I said this question could be voted to be closed as it may seem to be asking an opinion - and that would be an answer to me in itself as it would be down to developer choice but is there a DEFINITIVE reason to use node.js over signalr?
thanks
One reason to use node.js is code redundancy. Both the server and client run the same language, thus they may share a certain part of the codebase, meaning potentially less to write. With libraries like Browserify this process can be made a lot more transparent and writing the client-side can be almost indistinguishable from server-side development. Another opportunity this opens up is both client and server side rendering + MVC setups with, for example, rendr.js. So you can have both the fast load speeds of server-side and responsiveness of client-side rendering. If any of this will be useful naturally depends on what you are developing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
What advantages we will get if we use MEAN.js framework over our homegrown MEAN packaging? we are not going to use angular.js (A part of MEAN.js)
Will we face any API versioning issues? Will there be any issues related versioning of packages in MEAN?
Is it really complex to use MEAN.js as compared to creating own structure to use manage APIs, etc.
I was trying to create custom MEAN stack myself, but it was only a matter of time when i realized, that MEAN is not only MongoDB, Express, Angular and Node. Just look at node modules to see how many additional things there are. Authorization(passport.js), connectors, parsers, test libraries, mailer, promieses, etc. When i was starting I didn't find these tools useful, but now I would add most of them to my custom MEAN. Thats why I use MEAN.js stack
We can't possibly know whether your configuration will work better than MEAN.js because we know neither your needs, nor your configuration. MEAN.js provides an API out-of-the-box and supports scaffolding (via yeoman) which generates files and code with a single command. I am not a huge framework enthusiast in general, but I have to admit that development became much more easier and enjoyable since we switched to MEAN.js (ditching our own custom MEAN stack).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I have a Node.js script running locally through command line (I haven't developed it so not very familiar with the code) which takes an email address as a parameter and looks up some data and spits out results in a command line table.
I wanted to make a "front-end" for this, like a simple local Webpage where I could punch in an email address and see the response right on the browser itself.
I am not very familiar where to get started without complicating this into a bigger problem than it is. Any guidance would be very helpful here. I haven't really done any web development using Node or JS before but I am familiar with basic web development (and willing to learn) new ways of doing things.
If I can provide any additional information please let me know.
Thank you!
The most prominent framework for developing node apps is express.js. You can't go wrong if you invest some effort into learning express. It will help you with routing and templates, and can generate a skeleton application for you. Read through the guide, and learn:
http://expressjs.com/guide.html
Also you may study the answer to the most popular node question on this site:
How do I get started with Node.js
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
We are using this server for almost a year now.
Last forum post seen in November, 2011.
Last server version released 28/03/12.
Just wondering if anyone knows whats happening inside the company?
Should we expect something or should we start looking for alternatives?
I did what you did not do: using email to ask the question to the people able to answer.
And they replied that:
the forum was closed because they could not cope with the amount of accounts created daily to publish junk
the next version will be the most important ever made for G-Wan, with new features like a caching reverse proxy and an elastic load-balancer as well as system replacements like a wait-free memory allocator.
With regard to such developments, a 3-month period without publishing releases sounds reasonable.
More reasonable than assuming that such an 'inactivity period' means that "the project is dead".
Would you say that for other Web servers like Apache which have much larger release cycles?
You should always be expecting something from G-WAN. It's a great piece of software. Here's the other thing too: G-WAN was expertly engineered. That doesn't mean that there are no bugs in it, or that features can't be implemented, but G-WAN is incredibly tight.
It has lean code, it does what it supposed to do, very well, and it is built for the developer to add in the functionality that hasn't been put in there yet.
That's the beauty of it, or one facet of the beauty.