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.
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 last month.
Improve this question
I try to improve my career but at this moment I think how would I start again?
What is your opinion? What is the best way to start?
i wish to know the most relevant roadmaps in frontend developer
First of all, you must learn HTML and CSS. After doing that start learning Javascript. Then you can learn javascript frameworks like React, a free and open-source front-end JavaScript library for building user interfaces based on UI components, or Angular.
In beginning, I would suggest React as it has a large developer community and is also a bit easy to understand.
You will also need to learn about making API calls, so learn about rest APIs and postman.
Also, learn how to format the JSON you will get from the backend.
After that, you can work on learning Redux(state management tool) and typescript(a superset of JavaScript ).
TO SUM UP THE ROADMAP :
HTML
CSS
REACT/ANGULAR
REDUX
API
TYPESCRIPT (OPTIONAL)
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 6 years ago.
Improve this question
I'm trying to develop a program like Windows Live Messenger for fun and personal use, using Node.js for the backend part of the messenger, and I've come up with two questions:
Is Node.js a good choice for backend?
Which language(s) should I use for the frontend part?
Thank you very much.
The backend language doesn't matter at all. Python, node.js, ruby, perl, c#, java, scala, golang, as long as you expose an interface that can be consumed by the client. (generally a RESTful web service interface, but it doesn't have to be.)
The frontend language depends on the target platform. You should use the native language for the client platform for the most streamlined development experience. C# for windows, Java for android, Swift for ios, javascript for web. If you want to "write once run anywhere" consider React Native.
But be aware that any "write once run anywhere" strategy is going to be plagued by hard-to-debug cross-platform bugs, in practice it's almost always cheaper to maintain a client for each platform, because it's easier to debug in the native language.
Another alternative is Ruby. With http://reactrb.org and rails you easily put together such a system. In fact the tutorial on the above site ( under docs/tutorial) is a simple chat app
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 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
I've heard that node.js is really fast for applications like chats and real time apps.
I was wondering if node is a good choice to develop a forum or a q&a site like StackOverflow?
Yes it's perfectly possible, you don't have to implement your own web server like somebody said, you can just create it using something like Express (as a framework) and Mongoose (as a MongoDB ORM) or whatever you choose.
I think Node.js is a good solution for such a case because of its high concurrency (and Stack Overflow is a site where thousands of users are online in the same time probably). So yes you can achieve this with PHP, Ruby and Python etc, but I believe Node.js is a better fit (that's my opinion, based on the success stories I've heard which were based on Node).
Node isn't just a solution for building small services, here are some good examples ( https://nodejs.org/en/blog/uncategorized/an-easy-way-to-build-scalable-network-programs/ ).