Should you Learn Node js in 2017

Tricks, Ratschläge, Online, Reparieren, Landwirtschaft, Landwirtschaft Maschine

1. Some couple more notes on the topic:
   
   1) Frameworks and libraries can make your tasks easier, and Node.js is getting more and more of them as time progresses. React is one of the more popular ones at the moment.
   
   2) Popularity is important, and Node.js's popularity is growing quite a bit. If you ask for my personal opinion I think Node.js will become even bigger than it already is.
   
   3) Your comfort level with the language would make a difference too. If you enjoy coding in JavaScript it is likely you will enjoy Node.js development as well (although if you're new to web development it could take a short while to get to the "aha - so that's what it is!" moments).
   
   Also, this might be just me, but I feel there's a big open-source community revolving around js – so that's another plus if someone wants to grow their online portfolio by contributing to open source projects
2. If
   A) you want to build build the client and the server in the same language i.e. javascript
   B) you want something that has great IO performance
   C) you want to create mobile apps in javascript with angularJS or REactjs UI frameworks all without having to learn a new programming language or new libraries
   D) and you want to goto a platform that is portable, virtualizable, open and you can play with on your PC
   E) And scales well with the callback paradigm but does worker threads if you need threading that sort of functionality
   F) And you want something that suppports basic oo but isn't oo insane
   
   Then node.js(which is serverside javascript) is the way to go. It's been around now for 5 yrs and that's far longer than java was around when it got traction.
3. you go .net core dude.
4. Laravel for life WOOOOOOH.
5. yes, if you do backend you need to know Node.js. why? most likely there will be a sea change. It used to be that PERL was the goto backend language and PHP was considered cool but used features that "most" developers didn't need, until they needed them or just wanted them. OK, so why do we need node.js? cuz high performance is what we want out of a web app, fast networking is what we want out of a web app.
   
   Yes, you can learn ruby or python, but then you're stuck writing in two languages cuz you will write in javascript at some point. But the most important thing is that if you're PHP/Ruby/Rails, traditional front-end developers don't need to do a lot to start doing your job. Javascript frameworks and async functionality have already helped front-enders to start reaching out to the backend. developing a route in node.js is basically the same as developing a route in React or angular. as for all these 'high-performance' updates to other frameworks? these are reactions to Node.js.
   
   PHP and to a lesser extent Rails/Ruby are high-paid platforms, they may be free but there is a lot of money being made. Just think how badly WordPress needs PHP and PHP development to survive. So why leave? Cuz it doesn't last forever. For instance, when I stupidly learned ActionScript 3.0 and I should have taken that time to go back to JavaScript. It didn't seem like the glut of Flash work would ever dry up, it seemed like a Flash future until AS 3.0 and then it was basically gone. I had to play catch up with JavaScript. I'll also point out that it was shitty security that helped AS 3.0 fall, so you if you really think WordPress can't disappear overnight....
   
   Finally, end-to-end javascript development. I assure you, if you haven't dev'd your frontend/backend in one language 2017 is the fuckin' year to learn Node.js.
   
   Start with NVM
6. I agree that nodejs isn't the leader in the freelance market, but I still feel that having one language on both server and client leads to more straightforward and speedy app development. I also think the future of software development revolves around nodejs so it helps to have a good knowledge of it. Again, just like any other language or framework, nodejs is leveraged on other frameworks like expressjs and so on and the developer community is really good. Experimental or not, there are many libraries to choose from to get the job done, i cn say thesame for django, ruby and so on.
7. Anyone can suggest me why Use Node.js? and Where to use? Why Big Companies uses this? It is individual Language to work on it and it is good way to become career?
8. Thank you! This video was extremely useful.
9. Knowledge is power. Learn everything.
10. You lost me at 2:50 when you said "I have not used these" (e.g. express)...
11. what are the unique advantages of node js over the rest?
12. have you used python and Node ? would be great to know from a programming point of how does it feel to write code in two different languages - node vs python. Since node is JS primarily is it easy to structure your thoughts while coding in node, ' cause you don't have to think about syntax and Business logic at the same time ? I have heard eclectic views on this topic so people actually preferring two languages as they feel they it keep them thinking server side and client side
13. Isn't PHP 7 high performance enough?
14. I would say if you want to any kind of modern web development learning node.js is essential. If you want to do React, the only sane way to do it is using a bundler (webpack), which pulls in lots more dependencies such as babel and of course node. If you want to stay in the dark ages of web development, don't learn node.js. It's that simple
15. Good advice! Node is awesome, but unless you need a blazingly fast server-side for some type of Twitter application, there are more mature frameworks like Django, Rails, Laravel, which give you a lot more out-of-the-box functionality. But I must say, the future of Node looks promising, software is becoming more and more CPU demanding, and Node fits right into that paradigm.
16. The only negative of node at this point that I have heard is less support than others: everything else is a positive. If you are planning on learning something new, then I would say do so with node and as you become a pro at it, there will be a lot more support and structure.
    
    He uses the processing power example... There is a reason why processing power increases every year. Industry standard needs of clients increases every year. The performance we need now may be drastically different next year or the year after. Why invest your time learning into a server that seems has less "performance". It is just another tool in your developer belt. Never stop learning people.
17. Hey man, great video, but a I'd like to clarify a few things for those who may not choose to learn node on a few of the points.
    
    Regardless of whether you want to write your entire back end on node, chances are you will encounter it at some point for acquiring front end libraries (npm/bower) or leveraging tools like gulp/grunt for build automation, so whether you want to completely invest in it, it's good to at least know a little bit about it since most modern web development depends on it.
    
    Also, performance is good for asynchronous requests, however, not so great for CPU intensive tasks since javascript is single threaded. While you could use multiple processes, you would come out much further ahead by choosing a multithreaded language to handle long running processes and CPU intensive tasks. Node is very performant when discussing sheer volume of requests since the event driven architecture does not block new requests and does not spin up new threads on your web server, however, if any thread blocks due to CPU intensive tasks, it will block new requests. Also, new benchmarks for C# on the Kestrel web server are much higher and other frameworks are closing the gap, as well..
    
    Also, through tools like Electron and Ionic, node can be utilized for far more than just high performance web apps. Electron allows you to write cross platform desktop applications. Slack, Visual Studio Code, Atom editor (and many more) use this. Ionic is a framework built on node and angular that allows web developers to develop mobile applications without having to learn an entirely new skill set (i.e. Java, Objective-C, Swift, etc)
    
    Also, if you want to do real-time applications, then node has very good support for websockets (as do other frameworks) and is a great choice.
    
    While I don't agree that it is the "go to" platform for new developers looking to find work, it definitely has more to offer than just quick request i/o.
18. In passing, you mentioned that Node is more performant than Java. In almost all circumstances, that isn't true, Java will be considerably faster. I realise, of course, you were mainly comparing Node to php, ruby and python.
19. I already know Laravel(php)......should i go for node.js ? or advance to functional programming language.