Is Ruby/RoR obsolete?

Question

Ruby on Rails

Hello, dear ruby ​​and rail workers.
I'm fairly inexperienced in the back end and am currently in a state of searching. One way or another, I tried all the popular languages ​​​​and several frameworks, and settled on a strong feeling that Ruby and PoP are mine. But I still have some doubts and questions.
Recently, I quite often come across the thesis that RoR is slowly but surely becoming obsolete. Is it so? What, in your opinion, are the prospects for the language and rails itself in the web environment? Are there any progressive shifts, like, for example, PHP 7 in the PHP ecosystem, or is the trend the opposite?
And the second question - how suitable is Ruby for developing and maintaining large-scale projects in Russia? By large-scale, I mean tens of thousands of positions in an online store or hundreds of thousands or millions of pages created by users. Is it difficult in Russia with Ruby / RoP personnel?
Thanks in advance.

Answer 1

Recently, I quite often come across the thesis that RoR is slowly but surely becoming obsolete. Is it so?

No not like this.

What, in your opinion, are the prospects for the language and rails itself in the web environment?

It will continue to be a startup technology: high prices for freelancing, weak demand in offices (in Russia it is completely absent).
The coolest technology for making money remotely.

Are there any progressive shifts, like, for example, PHP 7 in the PHP ecosystem, or is the trend the opposite?

The paths of Rails and PHP frameworks diverge - the latter are moving in the direction of increasing rigor.

And the second question - how suitable is Ruby for developing and maintaining large-scale projects in Russia?

Absolutely not suitable.
In Russia, the technology is not widespread, look at hh: in Moscow there are only 6 vacancies with a salary of 130+.
In addition, enterprise technologies are better suited for large-scale projects: C#, Java, or even PHP.
So far, there are no tools in the Ruby world that are similar to those found in these languages.

Is it difficult in Russia with Ruby / RoP personnel?

Yes, ruby ​​artists will not go to the office: on freelance, income is 2-3 times higher.
The conclusion I will draw is this: RoR is a great technology for startups, but terrible for an enterprise.

Answer 2

Well, in the context of the fact that our average life expectancy is not long and we have already lived half our lives, we don’t give a shit, what difference does it make to us whether the language becomes obsolete when our grandchildren develop it?
Well, it really makes sense to think about what will happen after our death.
so reason drinking water will become obsolete faster

Answer 3

If everyone thinks that this is becoming obsolete, it is not fashionable, then everything will become obsolete and will not be fashionable ... As you wrote above, ordinary programmers do all this, these are open projects, instead of thinking about obsolescence or fashion is better to contribute to what you like.
Ruby is a very convenient and expressive language for me, it is very pleasant to develop in it. And not only "rails" lives the ruby ​​community.
In short: if you like it, do it and make this ecosystem better. There are people out there who write their own frameworks on pearl, a la Rails (modjolishes), and I don’t think how quickly it will become outdated, etc.

Answer 4

Rails are no longer a hipster trend, and that's a good thing. This means that the technology has passed a certain (teenage) stage and moved into adulthood. Rails are not dead, but continue to be actively developed and used in various projects. At the same time, new difficulties and questions arose: it turned out that the Rails were not very suitable for large projects, they were too narrow for them. Therefore, now there is quite a lot of criticism towards Rails, a lot of whining about ActiveRecord, a lot of talk about true OOP and other theorizing. In general, this all provides opportunities for the development of Rail and Ruby. But also many go to Go / Elixir / NodeJs and some other hipster stuff.
At the same time, the web technologies themselves do not change much: everything still works on HTTP, the same relational databases are still used everywhere, the vast majority of projects use a thin front-end. That is, we can say that as long as the web is alive in its current form, Ruby / Rails will live (as well as PHP / Python / any other language for the web).
Then forget about popularity and just work. Rails is a tool like any other framework in any other language: they allow you to do the same things. In the end, the result is important, the finished product is important. The quality of the product in most cases does not depend on the tool. Shit can be done on anything, shit can be done by good engineers, shit can also turn out for reasons beyond the control of the developer.
The weak point of Rails (or rather Ruby) is the lack of multithreading. Therefore, if the number of requests per second is critical, then Rails is usually not chosen and such projects are not made on them. Or they use JRuby, but this is somehow very rare.
Difficult, but not impossible. There is no mass character, but if you know how to work, you will not get lost.
I personally think that we need to strive for the West, because it is not clear what will happen to IT and the Internet in Russia.

Answer 5

What do you mean by "obsolete"?
What is already in RoR will be enough for 20 years - even if hack and ror die together. :)
You can ask a question on Twitter here, https://twitter.com/rubyunderhood