Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I used node for 1 year, but only for writing server applications. I am now interested in making an application that's usually written in a language like C or C++, so I am not sure if it's possible, for example, to write a keylogger or simillar applications using JavaScript and Node.js?
Yes, you can use Node.js to write desktop applications which can act as a keylogger, communicate with device drivers and other system resources.
Most of the system interoperability has gone into providing cross-platform support for particular system event notifications and I/O. Be mindful that there are tall stacks for reading keyboard events that differ from platform to platform, so you will probably want to take a look around the Node.js ecosystem for packages like node-ffi, which may assist you at accessing system resources from your application's event loop.
Should you want to write your own system bindings that are exposed to V8 and accessible by your Node.js application, there is excellent support for going native, from packaging to creating asynchronous events for your Node.js application.
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 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 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