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).
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 months ago.
Improve this question
Is it a wrong manner to start writing a NodeJS application using REST architecture, then try to use GraphQL or gRPC approaches in some parts or completely rewrite some or whole the application in the future?
The reason for doing this is previous experience and coding speed in REST APIs. But at the other hand it's kinda a big microservices project and should support millions of users.
GraphQL is not going to help you scale, quite the opposite in many cases. GraphQL is an optimization (in some cases) but mostly for developer productivity, but there is a complexity cost.
Generally I would suggest to steer away from this optimization unless you have a clear understanding of what you're solving for. REST is a good 'default choice' because it's well understood, requires little tooling and is pretty universal.
Once you are further into your project and you find that you have (ideally measurable) challenges, you're in a much better place to decide to use a more specialized paradigm (gRPC/graphql) and why, but it doesn't sound like you're there yet.
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 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 9 years ago.
Improve this question
What are your experiences with Node.js XMPP client libraries? What do you recommend?
I would highly recommed node-xmpp, which is the most idiomatic library available for Node, in that each connection is an EventEmitter which emits events in a similar manner to the built in modules.
If you are coming at Node from a browser-based background, the way stanzas are constructed is identical to Strophe.js, which minimizes the learning curve.
As you venture further into XMPP territory, node-xmpp is also a great way to write components. And its architecture is clean enough that there is even an xmpp-server project being built on it.
Finally, I'm also developing Junction, which is a suite of XMPP middleware, similar in style to what Connect/Express offers for HTTP. I'm currently building out examples and additional documentation, but the source code has full API docs, and I think its a solid framework, particularly if you are incorporating various XEPs into your client/component.
If you are trying to build a bot for Google Talk, I would suggest using https://github.com/simple-xmpp/node-simple-xmpp
Node-xmpp did not work for me while connecting with google's servers.
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