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.
Related
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 3 years ago.
Improve this question
What are the benefits of building react app with (NodeJs) over (Without Nodejs) ?
Thanks in advance
There are several advantages with using nodejs assuming you are referring to using nodejs to work with bundlers like webpack etc.
faster development with features like webpack devserver.
modern language constructs. with the kind of plugin ecosystem we are free to use modern language constructs without worrying about browser support. It may be true to some extent for embedding babel and other scripts but not very easy to manage after a stage
helpful in writing unit tests. as the testing config can share most of the development configurations.
features like instrumentation for code coverage can be easily done with minimal configurations
lot of processes can be automated. ex: localization etc.
A lot of things becomes easy and maintainable
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 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 9 years ago.
Improve this question
Am I right in thinking that node.js is a "total" development platform, in much the same way as asp.NET, PHP and even classic ASP are?
There seems to be a lot of excitement about node.js which makes me a little nervious about it being yet another "flash in the pan" type technology that will fade away?
If I was going to go about learning node.js have you got any tips how I might start out, without frying my brian?
Node.js is not a platform for common applications like blogs, etc.
It's for fast async apps like chats, relays, etc
It can be compared to Twisted framework (Python), Tornado framework (Python) or eventmachine framework (Ruby).
As said DmitryR, node.js is a framework of Javascript.
It is also based on the V8 engine of Chrome.
It is server side based, but can be used for non-internet application too (I m develloping one right now).
What is your goal in learning Node.js?
Create a website
Wrong choice
Create a web app (like a chat)
Good choice
Learning a new language ''for fun''
Good choice too, Node.js is asynchronous and quite easy to learn, even with obscure docs, and can be used for a lot of things. It is also a script, so it don t require to be compiled, but you better be on non-windows os, since node.js for windows can be a pain for devellopement.
If you want tips about where to start, you d better start by understanding asynchronous programming, it s the only "hard" part of this language.
There are some interactive ways to learn node.js like:
nodeschool
node.codeschool
You can give them a try.
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