Is Ruby really harder than PHP/Python? If yes, why?

Question

Ruby on Rails

Good afternoon.
I myself am a beginner web developer, I started with layout, then I mastered JavaScript and some related technologies, now I want to try my hand at back-end. For general development and broadening my horizons, I decided not to use Node.js, but to study some other environment / language. So far, I liked the Ruby syntax and its sharpness for web.
And now actually questions:
First.
Ruby/Rails books emphasize that this is for experienced programmers. Also in various topics, it is often mentioned that the barrier to entry into Ruby/Rails is quite high and development in the Rails environment is not for beginners. Is this true and what is the reason? What are the nuances and pitfalls? Why is ruby ​​more difficult, for example PHP, JS? Is it worth it to start with Ruby if you have never dealt with the server side before?
Second.
Let's say I studied the language itself, studied Rails and Sinatra. I made a couple of sites for training, launched them on a local machine ... Where should I go next? There are relatively few vacancies in this area, employers are looking for seniors right away.
So, how do you get to senior level? Or do you need to come to Ruby with several years of development experience in other languages ​​behind you? How do Rubists get their FIRST job? Please clarify this point.
PS
I am already over thirty, I started studying web technologies a year ago, I have no special education and connections in this area.
What are the chances of getting into the office as a junior, or a real prospect is JS / PHP and freelancing? (:
Can you help me figure it out? Thanks in advance friends!

Answer 1

And it's not about the syntax.
ror requires a good base.
The office is real, ror is difficult ─ you will need to compete with good middle/senior level specialists.
Why don't you like php/python ? Yes, and there are actually not enough js specialists, a lot of people can use jqury, but something more complicated than an intelligent specialist has to be looked for.
Do not spray, choose what to specialize in and go ahead, age is already playing against you.

Answer 2

I came into Rails development four years ago knowing absolutely nothing. Learned on the go. Along the way, I mastered SQL in the mode “here is a procedure in PL / SQL six screens long, it needs to work yesterday.”
Since then, there have been no fewer vacancies.
Another thing is that knowing Rails is not enough. We need a front, at least a little. Slim/HAML.
In the RoR environment, a fetish for tests means at least RSpec, Capybara. At least one background gem is delayed_job, Sidekiq.
Add to this the ability to deploy the whole thing and start in production - Capistrano / Mina, unicorn.
Appreciated to see at least once in a lifetime Devise and Cancan.
The rest usually depends on the project.
Next - the rules of good form.
https://github.com/bbatsov/rubocop
https://github.com/railsbp/rails_best_practices
https://github.com/bbatsov/rails-style-guide
And then you are suddenly a strong middle or a beginner senior and advice is usually no longer needed.
UPD : Yes, it's generally worth starting with Ruby/Rails. But my opinion is biased - I do not like PHP, although I respect NodeJS.

Answer 3

Why is ruby ​​more difficult, for example PHP, JS?

It doesn't seem more difficult to me, given that Ruby code behaves predictably.
Pull up the entire web development stack - git, sql, js with frontend frameworks (backbone, react...).
Some of those who are looking for seniors are ready to take on less experienced people. Especially if they like them.
I somehow formulated a rule for myself - a person must send 100 responses to vacancies before complaining that "there is no work."

Answer 4

Ruby is beautiful, but this is the beauty of a Japanese samurai with a sword against a company of soldiers with machine guns and an atomic bazooka at the ready in Python. Scary but effective. At first, Rubies really look magically beautiful, until you realize that beauty and efficiency are often different things.
(c) not mine

Answer 5

Easier. Because the language ecosystem is not fragmented.

Ruby/Rails books emphasize that this is for experienced programmers.

It is not true.
Those materials that I saw were designed for beginners.

Second.
Let's say I studied the language itself, studied Rails and Sinatra. I made a couple of sites for training, launched them on a local machine ... Where should I go next? There are relatively few vacancies in this area, employers are looking for seniors right away.
So, how do you get to senior level? Or do you need to come to Ruby with several years of development experience in other languages ​​behind you? How do Rubists get their FIRST job? Please clarify this point.

Make sites familiar for symbolic prices.

What are the chances of getting into the office as a june,

Near-zero is an unpopular stack in Russia.

Answer 6

not more difficult
, just initially designed more competently, therefore, supposedly for more experienced

Answer 7

First:
I would say that ruby ​​is not harder than javascript. In general, one of the simplest languages. But I can’t compare with python / php, I don’t know them. In general, languages ​​as such (i.e. syntax and language constructs) are not that complex. The complexity, IMHO, is in the technologies that are written in these languages. The technologies that are required from Java / C # developers, it seems to me, are much cooler (enterprise after all) than ruby ​​has.
I myself first of all taught RoR and only then ruby ​​myself.
Second:
For a beginner, the main thing is to show knowledge, then they will be hired. It’s just that some people don’t want to check this knowledge (or maybe they don’t know what they need or don’t want to).
My advice to you is to read and study everything. Learn git, command line and Linux in general, SQL, how databases work, dns, http, tcp/ip. Bookmark and save for later, someday all this knowledge will come in handy.

Answer 8

It is often said about Ruby/Rails that PHP is more difficult because deploying is more difficult, yes, but after trying a couple of times, you quickly get your hand in and get used to it. And the language itself did not notice that it is more difficult than PHP. I agree with thepry , not uncommon, due to more adequate behavior and predictability, even simpler than PHP. Andrei Nikiforov answered the rest of the questions in sufficient detail, and there is nothing to add.

Answer 9

www.youtube.com/watch?v=TZ-vZv1JXYY