I am no fan of it.. I've been stranded in it for over a year now and i
still loath it. I have to stay because the job looks like crud on my
CV, and when people ask me what i've doing i have to say Rails. Then
the interview switches to developing in Rails, and i can see a whole new
world of joy
If you have ten years of C/C++ you don't have to apply for Rails jobs. Just
apply for C/C++ jobs and when they ask why you did Rails just tell them you
felt like a change but it didn't work out. Lets face it 10 years of C/C++
should be most impressive. But you will have to articulate your dislike of
Rails in a considerably more professional way than you are expressing it
here. To be honest you sound like a whiner. You didn't get on with Rails,
big deal. I didn't get on with Java despite doing it for a few years. I
just politely decline Java jobs and thank them for their interest.
Don't let it fester, it will eat you alive.
Why i hate the framework for two reasons... 1 it touts ease and people
say (all over) that they can create apps in hours. The language is in
no way easier than c++ or java.
This is odd. Ruby is generally considerably easier than either Java or C++
because there are less things to actually do. In Ruby a class is a class,
in Java and C++ you have static classes, abstract classes so there are more
design decisions and the application source gets longer. In Ruby the
methods are either public, protected, private or class methods. Again less
decisions and less code to type.
Maybe dynamic languages are not your thing. Fine. No problem. Java is not
my thing but I'm ok with C and C++. People are different.
The logic and math is the same..
Setting things up to scale is no easier. To be honest many things are
significantly harder than java and c++.. At least when you want you
want to make things really perform. Which brings me to the second bit
of reason 1. The apps that get built in an hour, only amaze people who
have no idea what programming is. Why this makes me not like it?
Because my bosses, and their clients hear the bit about easy, and fast
and budget according to this. I have to fight with each new feature.
Ruby and Rails can indeed develop applications very quickly. But the code
on the whole is quite shallow and amenable to refactoring. You tell the
client that something can be put together very quickly but should they want
it extended in ways that were not part of the original design it could take
longer than they think. Perhaps the issue here is that you are trying to
apply BIG APPLICATION development practices from java and C++ in an
environment where Agile or XP would be better suited. It is not a
coincidence that the Ruby and Rails communities embraced Agile and XP, or
at least iterative development.
If I were to apply my mainframe COBOL or Fortran development practices to
our Rails applications it would indeed be a world of pain.
The second reason that i dislike the framework is because it lowers the
bar too much.
So what you are saying is that you can't stand the heat. Too much
competition and you have no way of showing how much better a programmer
than all these other guys who are actually interested in Rails.
The statement actually contradicts you earlier statement "To be honest many
things are significantly harder than java and c++" and the later statement
"The low entry breads lazy coders.. And they stay ignorant". How can it
lower the bar, which I assume you mean allows a lower quality of programmer
to take work from you, and be harder than Java and C++. Those are some shit
hot lazy bastards you got there. Send a few of them my way, my developers
have only one Phd between them
So much so that samples one finds when learning the
framework, they are often shown code that is bad in so many ways it
hurts my brain to think of it... But then the same people who produced
the samples say "well its just one way to do it". The low entry breads
lazy coders.. And they stay ignorant.
Ok. So now i sound like a real hater.. Here's the good of it. For small
low volume sites rails can get the job done. Rails sits on ruby, and
ruby sits on c. All the power one needs can be found.
Well Java only sits on C so doesn't the same apply here?
At one point C++ was just a preprocessor that kicked out C code so that
puts C++ in the same category as Ruby then
You need to leave that job solely for the sake of you mental health.