Backend developer on a node, rolling in?

Question

Node.js

Hello, I'm learning js, I'm interested in the backend.
I don't want to jump to php.
The city is big (there are vacancies in the node)
But everywhere experience + php or typescript or the node goes as a secondary technology to the front.
From here arose, sensations, possibly false, that:
they pass into the node from the front or from php.
Superficially node, attracts by the fact that one language (js). Please correct.

Answer 1

A matter of taste. I know JS but don't want to get into nodejs at all. Why do I need a node when php solves the same problems?
I personally like PHP, which is something to rely on. The stack dynamics are moderately dynamic and moving in the right direction rather than coming up with 100,500 solutions to the same problem. There is a solution - everyone uses it.
The fear of learning another language is not justified in your case. Try Python/Java/PHP. Find out where it's easier for you to look for documentation, the pleasantness of the syntax, the speed of development. Where you solve a problem from the world of the living, and not from the world of "How this thing works."
I somehow wanted to learn Haskell, wandered for a long time, but in the end I got the feeling that the language solves the problem for itself, and not for me. I was simply uncomfortable with everything in that language. Even the native editor ended with a critical error...

Answer 2

In today's realities, it makes no sense to learn a node. many are leaving it for golang, as they once switched from ruby ​​to a node.
If you like the back, then the same php, python, golang is a more reasonable choice.

Answer 3

nodejs to the server side is not always a popular solution, but I vote for ts on the back, or js + flow

Answer 4

In short:
a Node is either a real-time application (web-socket), or an IoT application, or a parser, or testing an existing site. That is, as a rule, this is an application that runs without an interface on the server side or on a specific device.
For the rest: PHP does a great job.
To create regular websites, it is better to learn PHP.

Answer 5

I write on the node because I like it, but the background with php
itself would be fine. Everything in the node would be fine, but not only product ready, so for a beginner in the backend on the node it will be complicated, everything seems to be there, but everything needs to be filed to customize. Knowledge of the language will not give any advantages.
And of course, typescript, this is exactly why I decided to write the same backend on the node

Answer 6

Node is an interesting tool for backing. Here the question is more in what interests you most? who do you see yourself as and what is easier for you - try to google materials on node, golang, lua, kotlin or java. Look at what seems easier for you to understand and study - in any case, knowing something from what I have listed is useful in any case, and then you will take on something else. I have been writing in php for the last few years, recently I started writing in Java. And in principle, I can say that it is easy for me, I mastered the entire base of the language in a few days, now I'm delving into the spring framework for java. Many right now praise golang in particular, and many people use it. So you can take it, for example. But I repeat, the main thing is that you like it yourself, it would be interesting and would be given without much difficulty. I once chose php to start development just because it is very simple and there are no such restrictions by default as in other languages ​​- you can code and write a bunch of crutches - and everything will work)))) But when you just start - this is normal. The main thing is to constantly improve your code, apply the best approaches, and so on. Read books by Martin Fowler. They are very helpful and cool :)

Answer 7

node is good. But in practice, it turned out that node is good for microservices, some kind of transport solutions, but the sad thing is that:
1. A matter of taste
2. The popularity of the language itself (an example ala Go is a temporary phenomenon, it came "noisy" and left .. - php - many find fault but millions of people develop something on the web on it every day)) python IMHO is something incomprehensible but local at the same time chats, websocket, etc. on the python itself
3. Read, poyuzat and dig something for the soul - yes it’s worth it. For that there will be an understanding for personal comparison. Otherwise, how many encoders = x2 opinions))