Is it realistic to be a pro at multiple web development technology stacks?

Question

PHP

Good afternoon.
The situation is as follows: I've been a PHP web developer for quite some time now. But lately, I have been very drawn to the web stack of Microsoft technologies, such as ASP.NET MVC, etc., I even launched a couple of projects on it and I am delighted with the experience gained. It would seem that quit PHP and code yourself in C#! But PHP is my main specialty, it's my bread and butter, and I really like the LAMP stack itself. By the word pro, I mean knowledge of how it all works under the hood, for example, for C # it's MSIL, CLR. At the same time, PHP and related technologies absolutely always have areas that need to be improved. It turns out that here and there a car for study.
Question: how not to slip into "enikey"? Is it worth seriously sticking to one technology but playing with others? What can you say?

Answer 1

I have a fairly successful friend who believes that "jacks of all trades" are now very much appreciated: both the frontend, and the backend, and understanding all sorts of things, as DevOps is fashionable now.
A teacher from the university, who also makes good money and seems to be not a fool at all - says that "understand MVC, MV ... ruby, python" - 3-4 hours (he works with embedded systems on the main profile)
I personally think that programming is a tool. And the language, platform, stack is just one of the components of solving a specific problem.
Obviously, you should not make a social network on perl, a forum a la phpBB on nodejs, or a landing page on erlang.
Probably the most important thing is interest and "suitable" projects. Suitable means:
1) on time (nothing distracts from a specific project at the moment)
2) meaningful (or well paid, or a lot of fun)
3) a good team or a good attitude if you do it yourself
4) fits well into the stack of interest, so as not to cram stack into the project and suffer.
Teaching is the most important thing in this profession. And different methodologies, views of different cultures of the language, different approaches to solving some problems - this, I think, is no less important than an in-depth study of one aspect.
PS
I don't think it's possible to give a working step-by-step guide on how to achieve success in different stacks. if there is one, it would be interesting to see for yourself