> Ruby is already not a super-popular language
is this opinion or fact?
> I also (personally) disagree with lots of the philosophy behind Rails.
You present this as reasoning but, doesn't make it wrong.
is this opinion or fact?
> I also (personally) disagree with lots of the philosophy behind Rails.
You present this as reasoning but, doesn't make it wrong.
In essence you are trying to say Rails philosophy is right and the other one is wrong ? This is exactly what's wrong with Rails too much opinionated that it makes me want to puke for it is promoting pseudo-science. Give us fact about any of the philosophy Rails uses, I remember, making too many SQL queries is "just fine".
My shorthand statement meant that I've never seen Ruby in the top 5 (rarely even in the top 10) languages.
http://www.tiobe.com/index.php/content/paperinfo/tpci/index....
Those rankings aren't perfect obviously. My personal experience backs it up: Ruby/Rails is often the framework startups use to build MVPs, but I know a lot of companies that then switched languages (or sometimes switched to other Ruby frameworks).
By and large, most organizations that start out on rails have little reason to switch to something else, because rails can get you very very far. Can you scale it to twitter level without making changes? probably not. But most don't ever come close to twitter scale, and those that do couldn't have gotten there without rails in the first place.
I don't like working with Java personally, but it's much easier to staff a Java project than a Ruby one.
A good measure of how useful a framework is for business is this: how long does it take a programmer with no familiarity with the framework to pick it up? Meaning someone with programming experience, but nothing specific to this code?
That has nothing to do with how the code performs and everything to do with how well the code is organized and whether it does "surprising" things.
Also, rails is easy to pick up. It's continuously groomed and improved. Ruby itself is lends itself to expression. It's also a very well organized codebase.
It's been around for 10 years. People have been saying it won't last, that it'll never gain traction, but that's nonsense. It's a tool out there that you can use, and I as well as many other people enjoy it. Nothing wrong with that. It's a choice, an opinion. And you can get a job working with it if you want. you don't HAVE to use it, if you don't want to. if you want to use java, go right ahead. I could never, and will never.
But at the end of the day, i love the web, and I love ruby, and I'm grateful I get to do both at the same time, and if the OP wants to as well, they can. There is no reason to not learn rails if it's something your interested in and are considering it as a career possibility.