It is better to learn after a front-end-a, Node.js or PHP??

Hi. I'm a front-end dev, learn now React, really like. I have a desire to get acquainted with the back-end, for this I wanted to start to learn Node, what would my whole stack was on JS, but I understand that it(the node) is more complicated PHP?? In General tell me to which language you should pay attention to, and why.
Regarding the RFP will ask stupid question which one is more profitable? :-)
On the Internet looking for, but your conclusion couldn't do..
I would be grateful for any info..
June 14th 19 at 20:33
9 answers
June 14th 19 at 20:35
I'm a front-end dev, learn now React, really like.

It is better to learn after a front-end-a, Node.js or PHP??

Type already know all about the frontend? How to write in React? How to configure webpack? When using webpack and when rollup? What babel plug-ins/presets to use and how to configurate? As the application architecture to define, then to sleep at night? When it is necessary to make the logic in the middleware/saga, but when a thunk? How to keep SOLID in frontend development? The ecosystem also all probably mastered? now/Next/SSR/CRA?

I've been in the web field 6+ years of spinning, of which the last 2 to React. And I still ask some of these questions. Of course, there are good working practices derived from personal experience and/or experience of colleagues, but these issues arise still.

Then decide for yourself. Either is fine in frontend sort it out still, or drive in and jump on the back.
Salary - I don't think there is a big difference. A friend of mine gets $3000+ (purely React and nothing more) all the time and gets offers for more salary jobs.
what "this" rollup someone is considered an important moment?
Or here saga vs thunk, what is this? Voodoo? You take out the logic in the thunk?
saga, nobody except the inner circle of the Creator does not use?
Advanced rxjs to write, and saga only use who did not become advanced
but think if you listen to those who are the loudest shouts, they then will.. Six years and all these questions? You probably latent party animal that party and not hanging out and doing nothing does :) - lester_Sta commented on June 14th 19 at 20:38
thanks for the very authoritative opinion - vito.Hoeg commented on June 14th 19 at 20:41
and the authority? It is important for You as a human reputation? So You are one of those who listens to the screamers pegajosa own reputation, because they earn money. - lester_Sta commented on June 14th 19 at 20:44
I'm just a realist. I see rx in angular, react, java, android, C# see it is that the mass will use TOMORROW. But saga I do not see. I see and hear about it only from its creators. Is there a plus sign can something affect? No, but they can persuade You to saga. - lester_Sta commented on June 14th 19 at 20:47
I have not written that "all" know in front-end. Thanks for the old! - godfrey73 commented on June 14th 19 at 20:50
it's good that You understand it. I have met many people who thought that next to grow nowhere else. I Wish You Success.) - vito.Hoeg commented on June 14th 19 at 20:53
What sore of CDA, the author of the comment. Can see a picture of where these people spend hours on questionnaires, as a hunter in the bushes and looking for an insult to their profesionalnih senses or syntactic inaccuracies from asking questions. I love you. - michel69 commented on June 14th 19 at 20:56
June 14th 19 at 20:37
I've chosen C# core.
But if you start from what you already know JS then take the Node.
Here's an excellent screencast on Node
June 14th 19 at 20:39
I for Node
June 14th 19 at 20:41
Node.js due to the comfort when at the front and buck's JavaScript. A database is any database that uses JSON for example MongoDB.

It is also worth to look in the direction of Ruby on Rails
Do not teach bad. In the General case, you need a RDBMS - lester_Sta commented on June 14th 19 at 20:44
June 14th 19 at 20:43
Try both
June 14th 19 at 20:45
If you select node, you have to be prepared for the fact that you have to deal with asynchronous code. So you need to figure out how to work colbecki, promises and event loop as a whole.
The toaster is filled with questions for the nod, from those who do not understand how asynchronous code works.
June 14th 19 at 20:47
The problem is that handy and then, and then.
Node will be useful to build a frontend such as Web sockets on the server. But to write on it some major service will be quite difficult (though possible).
The main content is easier to generate from PHP.
But all depends on tasks.
June 14th 19 at 20:49
JVM languages to try.
After liberties that allows PHP (unless you php 7 came to teach) much more pleasant. In addition, the strong typing reduces errors and dramatically reduces support costs. Well, a great legacy JVM as a plus

PS Noda of course the mainstream but when libraries can be decorated in different styles (from Kabakov to classes ) it is very inconvenient and ugly.
June 14th 19 at 20:51
The question is fundamentally misplaced. Not what to teach after the frontend, and in parallel. You can't learn the front, it changes so that what you use today, tomorrow is already obsolete. In General it is correct to teach that require production tasks. Learning "on the table" in this area is meaningless. it seems you have problems with formulirovkoy - lester_Sta commented on June 14th 19 at 20:54
my apologies =) - vito.Hoeg commented on June 14th 19 at 20:57

Find more questions by tags JavaScriptBackendPHPFrontendNode.js