3 ms·

I have a general question. More along the lines of "what's the best practice in this situation." My first RoR app (recurseapp.com) now has close to 800 signups,

I have a general question. More along the lines of "what's the best practice in this situation." My first RoR app (recurseapp.com) now has close to 800 signups, and about 100 active users. It's also my only live RoR app. Now with the advent of Rails 3, my app is stuck in a limbo of sorts. I'd like to upgrade it to Rails 3, but a few gems I'm using are really resisting the upgrade, and what's worse is that there's been no movement in their git-repos for quite a while now. I know the best bet is probably to dig into these gems and fix them for Rails 3, but I really don't feel I'm that skilled a ruby programmer. Thoughts?

vgurgov 16y ago
I can see 2 possible solutions: 1) Dig into your problems with these gems and either fix or replace them 2) Think again if you really need Rails 3. What are some benefits that you will get from that upgrade? I'd suggest 2 approach. Rails 2.3 is a very solid version and is used in many apps. I don't see reason to "upgrade for upgrade". Especially if there is some friction and not enough time. I recently made very small project on Rails 2 just because all I needed was ActiveScaffold(not available in Rails3 atm)- which is really awesome for some stuff btw.
- Breefield 16y ago
  I've played with ActiveScaffold and can't say I'm as much of a fan :p My app is currently running on 2.3.5 – I think the reason I feel compelled to upgrade is that I just hear so much about Rails 3. Good point with the 'upgrade for upgrade' point. I'll have to think about it, and yeah, it is just friction at this point.
  - fendale 16y ago
    I've just spend half a day today trying to upgrade my rails 2.x app to Rails 3. I think I am going to give up on it, as it is breaking things everywhere. The UJS is the main problem, as I have tons of AJAX things going on, and quite a few things that are not really done the 'rails way' (I was learning as I developed this App). I guess this app is destined to stay at Rails 2 and I will just start a new one for Rails 3, once I get a good enough idea!
corprew 16y ago
what gems are being a problem? there are frequently equivalents to the gems with similar APIs that do work with rails3. The rails community tends to be fickle and switch to 'next big things' a lot, which causes a bit of churn like this over time. anyway, if you list them we might be able to make some suggestions.

vgurgov 16y ago

I can see 2 possible solutions: 1) Dig into your problems with these gems and either fix or replace them 2) Think again if you really need Rails 3. What are some benefits that you will get from that upgrade? I'd suggest 2 approach. Rails 2.3 is a very solid version and is used in many apps. I don't see reason to "upgrade for upgrade". Especially if there is some friction and not enough time. I recently made very small project on Rails 2 just because all I needed was ActiveScaffold(not available in Rails3 atm)- which is really awesome for some stuff btw.

Breefield 16y ago
I've played with ActiveScaffold and can't say I'm as much of a fan :p My app is currently running on 2.3.5 – I think the reason I feel compelled to upgrade is that I just hear so much about Rails 3. Good point with the 'upgrade for upgrade' point. I'll have to think about it, and yeah, it is just friction at this point.
- fendale 16y ago
  I've just spend half a day today trying to upgrade my rails 2.x app to Rails 3. I think I am going to give up on it, as it is breaking things everywhere. The UJS is the main problem, as I have tons of AJAX things going on, and quite a few things that are not really done the 'rails way' (I was learning as I developed this App). I guess this app is destined to stay at Rails 2 and I will just start a new one for Rails 3, once I get a good enough idea!

corprew 16y ago

what gems are being a problem? there are frequently equivalents to the gems with similar APIs that do work with rails3. The rails community tends to be fickle and switch to 'next big things' a lot, which causes a bit of churn like this over time. anyway, if you list them we might be able to make some suggestions.