Do you think there is no criteria worth considering besides the size of the hiring pool? What if 2 hiring pools are sufficiently big, do you still pick the bigger one every time?
> Do you think there is no criteria worth considering besides the size of the hiring pool? What if 2 hiring pool are sufficiently big, do you still pick the bigger one every time?
It is not just a hiring pool.
Look at various third-party SASS tools, they see Ruby as a second-grade language to support.
That's not at all my experience. There's a one-line integration between almost everything under the sun and Rails (business/traffic analytics, performance/profilers, error notifications, logging, object storage integration, I could probably go on). Many other frameworks don't even have the general capability of doing one-line integrations.
You're right. Those shouldn't be completely ignored. They probably shouldn't be the only argument to make tech decisions upon.
Did you ever build any webapp in Ruby on Rails? You should check it out!
Rising from #10 to #5 seems to imply that a lot of people are making 'questionable' decisions. As an active senior RoR dev since like 2014ish seeing that makes my heart atwitter :)
Rails 8 can make you a one-person framework and a successful SaaS solo-owner. Don't really care about the declining market share imo, I love and embrace it despite its shortcomings.
Do you think there is no criteria worth considering besides the size of the hiring pool? What if 2 hiring pools are sufficiently big, do you still pick the bigger one every time?