Do you know how node. js is on fire? Do you know what is the average wage for node. js now? Did you know that node. JS will continue to fire in 2018? Don't even know? Then come to the article, learn more node. js, maybe later your salary will be higher than the average salary of Nodejs, see this article together
First, let's see how node. js Fires up:
When node. JS is not up yet, the twisted developers have long known that only async is bad, and when they know that the language is Erlang, they start to recommend using Erlang. When node. js just came out, it wasn't, obviously, a comparison with Erlang.
Marketing done well is the key to node. JS fire up.
If you remember the number of lines that wrote an IRC slides. In general, the author of node. js, when comparing Event-driven and Apache with the fork process, is well-reasoned to point out the merits of event-driven. But in contrast to other models, he was talking about feelings. He said it would be an illusion to distinguish between the invocation of an operation that cannot be returned immediately and the general function call. In this way, only the asynchronous callback can be written into an advantage immediately. The most deadly shortcomings of node. js are packaged into advantages, and no moral integrity to motivate a group of people to engage in meaningless benchmark, immediately avoiding the unfavorable situation. Shouting slogans is always the easiest, event-driven is high performance, library is a burden, asynchronous callback hell is good is good is good. The fire got up.
In fact, say Nodejs really rely on marketing fire up? The fact is certainly not, marketing knowledge auxiliary means only. When the original Nodejs out of all kinds of bugs, simple test of its large file transfer will appear a variety of problems. Other camps in the same period had already dumped several streets. But why do you keep growing? Just by the so-called marketing and flicker?
If only isolated to consider the Nodejs of the asynchronous library in the end, it is too one-sided, is it NODEJS only provide asynchronous network IO?
In fact, Nodejs provides a common set of asynchronous infrastructures that allow you to build various asynchronous APIs based on this. Asynchronous network IO is only a specific application on it. And now the twisted mentioned in the question actually does not have the comparability with Nodejs at this point at all!
The reason I chose Nodejs is largely because it is JavaScript, so that I can complete the project in the same language in the front and back, which is a great advantage! In addition, although Nodejs is not unique, it is not the first JavaScript-based service-side scenario. But it's the best in the same time performance JavaScript camp.
Plus the LIBUV design at the bottom of the Nodejs is simple, very easy to expand, and NPM is so useful. As a result, development efficiency has risen rapidly.
Choose Nodejs in the end why, in fact, now, many people have their own reasons. But many people are because he is a low-cost solution based on JavaScript. (For more information about node. js, go to topic.alibabacloud.comnode.js Video tutorial section)
We should now understand why node. js is so hot, so what do we say about node. js in 2108, that is, can we continue the fire this year?
Let's look at a picture:
This diagram illustrates a number of issues, although node. JS is no more than the other languages, but the benefits of node. js are not as good as many languages. So it's important to learn node. js, and I wish you all a good job.
This is the treatment of node. js. Hopefully, node. JS can keep on fire.
A summary of node. JS:
In fact, now what Java,. NET, PHP Any grab can have a lot of Daniel Master
These technologies are very mature and Nodejs master great God really hard to find, Nodejs is really a small crowd of technology
But its future development is immeasurable, and the technology is not divided into the same. For the technology is not high God what the code
It is written by people, so it depends on the person who rides it.