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

Anton Antonov2017-10-03 11:50:41

PHP

Anton Antonov, 2017-10-03 11:50:41

Hello. I'm a front-end dev, I'm currently learning React, I really like it. I had a desire to get acquainted with the back-end, for this I wanted to start learning Node, so that my entire stack would be in JS, but I understand that it (node) is more complicated than php ?? In general, tell me which language is worth paying attention to, and why.
As for the salary, it will be stupid to ask which one is more profitable? :-) I
searched on the Internet, but I could not draw my own conclusion ..
I would be grateful for any information ..

Answer the question

In order to leave comments, you need to log in

9 answer(s)

Mikhail Osher, 2017-10-03
@miraage

I'm a front-end dev, I'm currently learning React, I really like it.

Do you already know everything about frontend? How to write in React? How to set up webpack? When to use webpack and when to use rollup? What babel plugins / presets to use and how to configure them? How to set the architecture of the application, so that later you can sleep at night? When should logic be moved to middleware/saga, and when to thunk? How to comply with SOLID in frontend development? Have you mastered the entire ecosystem too? now/Next/SSR/CRA?
I've been in the web area for 6+ years, of which the last 2 are on React. And I still ask some of these questions. Of course, there are good working practices drawn from personal experience and/or the experience of colleagues, but these questions still arise .
Decide for yourself here. Either get it right in the frontend still decently, or score and jump to the backend.
As for the salary, I don't think there will be a big difference. A friend of mine earns $3000+ (purely React and nothing else) and gets offers all the time for higher salary jobs.

Alex493049469, 2017-10-03
@Alex493049469

I chose C# asp.net core for myself.
But if you start from the fact that you already know JS, then take Node.
Here is a great Node screencast

Denis Tolstunov, 2017-10-03
@Tovstoi

I am for Node

Maks_Semenduk;, 2017-10-03
@sh13max

Node.js due to convenience when both at the front and at the back of JavaScript. And for a database, any database using JSON, such as MongoDB, is ideal.
It is also worth looking in the direction of Ruby on Rails

Anton, 2017-10-03
Reytarovsky @Antonchik

Try Both

Ivan, 2017-10-03
@LiguidCool

The problem is that both will come in handy.
Node is useful for building the frontend and, for example, Web sockets on the server. But writing some large service on it will be quite difficult (albeit realistic).
The main content is easier to generate from PHP.
But in general it depends on the tasks.

Vyacheslav Uspensky, 2017-10-03
@Kwisatz

JVM languages try.
After the liberties that PHP allows (unless you are going to learn PHP 7) is much more pleasant. In addition, strong typing reduces errors and drastically reduces maintenance costs. Well, the huge legacy of the JVM as a plus
PS Noda is of course mainstream, but when libraries can be designed in different styles (from callbacks to classes), this is very inconvenient and ugly.

Evgeniy Kvasyuk, 2017-10-03
@EvgeniyKvasyuk

The question is fundamentally wrong. Not something to learn after frontend, but in parallel. You can’t learn the front, it changes so that what you use today is no longer needed by anyone tomorrow. In general, it is right to learn what production tasks require. Studying "on the table" in this area is meaningless.

xeywar, 2019-04-16
@xeywar

First PHP then Node.js. In general, it's good to first understand what Node is mainly used for and where it is more appropriate to use PHP. And so I would use Golang, since there is no cooler on the back yet, but unfortunately this language is known to few people and few people need it.