2 ms·
It's not always about performance/scale. Often, it's about being able to find engineers to work on it. I don't like working with Java personally, but it's much
by smt88 11y ago
It's not always about performance/scale. Often, it's about being able to find engineers to work on it.
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.
- meesterdude 11y agothere is not a shortage of ruby engineers, nor of jobs to be filled for them. 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.