Does anyone who USES Rails hate Rails?

Rails
21

On 2 May 2013 13:18, Wins L. [email protected] wrote:

Jacek P. wrote in post #1107534:

It seems that I modify
problems to fit them into Rails instead of modifying Rails to adapt it
to my problems.

Well said. 100% right.

Wins L.: how long have you been using Rails?

Colin

22

On 03/05/2013, at 12:09 AM, Matt J. [email protected] wrote:

On Thursday, 2 May 2013 05:19:17 UTC-4, Bigos wrote:
I hate Rails sometimes. Now and then I have a feeling that using Rails is like
trying to fit a square peg in a round hole. For example Active record doesn’t fit
my every need and sometimes I have to use SQL. Because I use Rails I have lost
much of my SQL skills. Last time I had some unusual problem it took me 6 hours to
write a query. It seems that I modify problems to fit them into Rails instead of
modifying Rails to adapt it to my problems.

Similarly, I’ve found that using C has really weakened my assembler skills.
(trollface)

–Matt J.

Hehe.

It’s not Rails that’s a problem here, per-se, it’s ORMs that the OP
seems to have a problem with - shaping his application architecture
choices. Maybe he should be using MagLev and therefore Gemstone :wink:

I agree that ORMs tend to make you think un-object-orientedly
sometimes… but usually they can be worked around, and they provide a
good pragmatic “best fit” for most uses. It’s pretty darn good for free!

Julian

23

Colin L. wrote in post #1107600:

On 2 May 2013 13:18, Wins L. [email protected] wrote:

Jacek P. wrote in post #1107534:

It seems that I modify
problems to fit them into Rails instead of modifying Rails to adapt it
to my problems.

Well said. 100% right.

Wins L.: how long have you been using Rails?

4 month. Both Ruby and Rails. Previous experience 1.5 years in PHP, Zend
Framework 1 and 2, was testing Python + Django. And after ZF Rails to
me:

  1. is complicated
  2. is occasionally comfortless
  3. source code and its organisation is incomprehensible and scary
  4. I cannot make any step right or left. Use only what is offered and as
    written in their guide and API.

But I hope, yes I hope that this will pass when I gain more experience.
But for now I can say for sure that I wouldn’t develop my own project in
Ruby and Rails. Don’t understand why people around want their projects
in Rails. The only explanation (imo) is a good marketing.

24

I’ve been using Rails since 2004 and still love it. I understand a lot
of
the complaints about Rails and may have occasionally voiced my dislike
as
well. However, the complaints I often hear about Rails has more to do
with
the kind of coders/people the framework seems to attract than the actual
framework itself. By itself, Rails is an easy to use MVC framework
which
can help you get a website running quickly. It’s well-designed and
modular. It’s built on top of a great language, Ruby.

Really, Rails is just like any other tool. In the hands of a
third-grader,
a pen can create a a bona fide mess. In the hands of an artist, it can
create something inspiring.

25

I agree that ORMs tend to make you think un-object-orientedly sometimes

Isn’t the primary purpose of ORM to provide an object oriented way of
dealing with your data ?

I’ve been using Rails for 4 years, and I don’t complain. I can ask an
absolute beginner in rails to build something for me, and I still get
fairly modularised code thanks to the conventions, which make things
suck
less for the beginners. I agree novice programmers using Rails find the
framework an excuse to write code without thinking about important
things
like SOLID principles. But I guess that’s better than a beginner writing
code without a framework and not thinking about SOLID. For me, the
conventions are not obstacles, most of the time they help me from going
astray. If there’s something that doesn’t fit my needs, I can always
write
my own piece of code. From my experience, a frustrated day at work
would
usually be caused by bad programming and rarely the framework.