a year of rails magic

After working professionally with Ruby on Rails for a year, I decided
to write an article on my experiences with the framework.

http://nathany.com/developer/rails-magic

Since I detail a number of things that I found unintuitive or could be
improved upon, I am posting a link here on the Rails Core in hopes to
stimulate David Heinemeier Hansson and the core team towards an even
better 3.0 framework. I don't expect everyone to agree, and somethings
I don't see changing, but I post it never-the-less.

- nathan.

After working professionally with Ruby on Rails for a year, I decided
to write an article on my experiences with the framework.

http://nathany.com/developer/rails-magic

Since I detail a number of things that I found unintuitive or could be
improved upon, I am posting a link here on the Rails Core in hopes to
stimulate David Heinemeier Hansson and the core team towards an even
better 3.0 framework. I don't expect everyone to agree, and somethings
I don't see changing, but I post it never-the-less.

Hi There,

Thanks for taking the time to post here and share your thoughts,
while I don't necessarily agree with everything you've mentioned, I
appreciate that you took the time to say it.

One point I'd like to really highlight is:

"One adjustment coming from products like ColdFusion is to recognize
Ruby, and Rails as open-source communities. Rather than complain about
the dreaded wontfix tickets, we can get involved by submitting and
testing patches, and bringing them to the core teams' attention
through the mailing list. Become a collaborator. "

This is great advice, especially for people coming from a 'big vendor'
background!.

I wonder if I could suggest considering it when you look at ticket
6000. While this patch no longer applies cleanly, if you took the
time to rebase it against trunk and resubmit it, I'm sure we'd be
happy to apply it. Don't assume we're actively disregarding patches
that are in the tracker, we're on top of the reviewed patches list and
spend a lot of time trying to stay there.

The steps for patch reviews are listed at http://dev.rubyonrails.org/,
people here would be happy to help out, as would the guys in
#rails-contrib.

Thanks again.

Hey Michael,

Thanks for letting me know what the case really is, I never had
thought of that. I guess it's a matter of communication, because I
think anyone in my situation at the time would have been disappointed
to find a ticket for the problem with a patch from a year ago that
wasn't applied back then, or clarified as to why it sits there now,
as
you have just clarified. I also think many people consider themselves
users of Rails, and not yet familiar enough with the innards to
really
contribute... but hopefully that will change.

I hope I didn't come across as strongly disliking Rails, I don't. What
I am tired of is announcements of Rails clones, as I've pointed out
there is still room for improvement or doing things differently. I
hope to see that happen in one way or another, whether that be in
later versions of Rails or otherwise. I recognize certain things about
Rails aren't going to change... I don't see it ever adopting the style
of modularity of Django, but I do see that third-party "plugin
enhancers" are already getting better support from the core team.

- nathan.

Thanks for letting me know what the case really is, I never had
thought of that. I guess it's a matter of communication, because I
think anyone in my situation at the time would have been disappointed
to find a ticket for the problem with a patch from a year ago that
wasn't applied back then, or clarified as to why it sits there now,
as
you have just clarified. I also think many people consider themselves
users of Rails, and not yet familiar enough with the innards to
really
contribute... but hopefully that will change.

I think that it could be worth updating trac's templates to explain
the situation a little better.

I hope I didn't come across as strongly disliking Rails, I don't. What
I am tired of is announcements of Rails clones, as I've pointed out
there is still room for improvement or doing things differently. I
hope to see that happen in one way or another, whether that be in
later versions of Rails or otherwise. I recognize certain things about
Rails aren't going to change... I don't see it ever adopting the style
of modularity of Django, but I do see that third-party "plugin
enhancers" are already getting better support from the core team.

Some of the things you mentioned such as generating the schemas from
the models are not on the cards, otherse like improved threadsafety
are. The easiest way to make them happen is to chip in. :slight_smile: Several
of our 2.0 features came from external contributors, and I expect the
same to be true for 2.1.

Thanks again, and I hope *I* didn't come across too hostile :slight_smile:

No, no, thanks for taking the time to read my article. Much
appreciated.

- nathan.