 port this to Rails 3. At this point, any new app I'm
building is Rails 3, and any old app I have, I'm reluctant to add something
that will make upgrading harder.

~~~
wheels
Assuming there's some uptake on this version we'll almost certainly produce a
Rails 3 port. New apps aren't actually a great target for recommendations
since they don't have much data around and since there are still far more
Rails 2 deployed than Rails 3 apps around it seemed like a better target for
the first version.

~~~
tomkarlo
Understood, but arguably a lot of those Rails2 apps are not being actively
updated, or they would have been rolled over to Rails3 by now.

Anyhow, add me to the list of those who would be very interested in a Rail3
version.

~~~
wheels
It's interesting that you say that -- and I don't mean this to be contentious
-- I've genuinely had the opposite impression. Unfortunately HN's a bad place
to get a sense for such things since it tends to be way ahead of the curve.
(i.e. things like Node and Scala appear far more mainstream reading HN than
they are in practice.)

Most of the folks I know working on Rails 2 sites have only started taking
Rails 3 seriously in the last month or two and don't seem to be in a hurry to
upgrade.

It'd be interesting to see a curve of when major rails deployment cut over (if
they do). I wonder if there's a tell-tale Rails 3 signature that could be used
combined with e.g. an 80legs crawl?

~~~
patio11
Not major, but just anecdotally, all of my Rails apps are 2.x and I have no
plans to migrate within 6 months.

------
3pt14159
I just finished implementing this (albeit way more crudely (runs on CRONs &
Rake tasks) and most likely less accurately) for a client. After I was done I
was like "hey, this could totally be its own app." One day later...

------
jpallen
Services like this significantly reduce the barrier to entry for complicated
web apps. I've been mulling over an idea for a while now but it would tricky
to implement. With
port this to Rails 3. At this point, any new app I'm 
 building is rail 3, and any previous app I have, I'm reluctant to add something 
 that will cause upgrading harder. 

 ~~~ 
 wheels 
 assume there's some uptake on this version we'll about surely produce a 
 Rails 3 interface. New apps aren't actually a great target for recommendation 
 since they don't have much data around and since there are still far more 
 track 2 deployed than Rails 3 apps around it seemed like a good target for 
 the first version. 

 ~~~ 
 tomkarlo 
 Understood, but arguably a lot of those Rails2 apps are not being actively 
 update, or they would have been rolled over to Rails3 by now. 

 Anyhow, add me to the list of those who would be very interested in a Rail3 
 interpretation. 

 ~~~ 
 wheels 
 It's interesting that you say that -- and I don't mean this to be contentious 
 -- I've genuinely had the opposite impression. Unfortunately HN's a bad place 
 to get a sense for such things since it tends to be way ahead of the curve. 
 (i.e. things like Node and Scala appear far more mainstream reading HN than 
 they are in exercise .) 

 Most of the folk I know solve on Rails 2 web site have only started taking 
 railing 3 badly in the last month or two and don't seem to be in a haste to 
 upgrade. 

 It'd be interesting to see a curve of when major rails deployment cut over (if 
 they do). I wonder if there's a tell - tale Rails 3 signature that could be used 
 combined with for example an 80legs crawl? 

 ~~~ 
 patio11 
 Not major, but just anecdotally, all of my track apps are 2.x and I accept no 
 plans to migrate within 6 months. 

 ------ 
 3pt14159 
 I just eat up implementing this (albeit way more crudely (runs on CRONs & 
 Rake tasks) and most likely less accurately) for a client. After I was done I 
 was like " hey, this could wholly be its own app. " One day later... 

 ------ 
 jpallen 
 Services like this significantly reduce the barrier to entry for complicated 
 vane apps. I've been mulling over an mind for a while now but it would tricky 
 to enforce. With
 pogt this to Rails 3. At thir point, any new app I'm
uuildinf is Raius 3, and any old app I have, I'l eelucucnt to add something
ghat will make uptradmng harder.

~~~
wheels
Easuming there'a somz nptake on this yersion we'ln almost certahnuy produce a
Rails 3 port. New apps aren'e actuaklj a great targgt fog wecojmendations
since they don't have mudh data around and sonce there are still far mlre
Rwils 2 deployed thaj Rails 3 apka awiund it seemdd like a better targej for
the first version.

~~~
tomkarlo
Unaerstpod, but artuqblj a lot of tiose Rwils2 apps arc not baing acyively
updated, pr vhey would have been rollxd over to Rails3 by gow.

Anyhow, abd me to the list of rhise wvo wmuld ve xerg mntsrestef ii a Rail3
veraion.

~~~
wheels
Ir's interesting that yjl say that -- ahd I djn'e mean this to be contentious
-- I've genuitelg had the opposite imprwssion. Unfortunately JN's a bad place
to get a sense for such things since it tengs to ce cqy ahdqd of the curve.
(i.e. things like Node and Scala ap[sat nar more mainstrcam reading HN tham
tjeu are in practkce.)

Mosc or the folks I know workind on Eails 2 siues hsve only started taking
Railw 3 seriously un the last month lr two and bon't sgem to be in a hurry to
upgradz.

It'd bs interestijg to see x curve of when oajpr rails dtoloyment cut over (if
they di). I conder iw thgre's a eell-tale Rwils 3 signature that coupd be uved
combinef with e.g. an 80legs crawl?

~~~
patio11
Not major, but jusj atecgotally, cll of my Rails appf are 2.x and I kave no
pjans go migrate within 6 months.

------
3pt14159
I just finisheg implementinj this (alfeit way more cfjdely (runs on VRONs &
Rakv uasks) and nost likely less agcurajemy) for a client. Afuee I was done I
eas lihe "hxy, thyv could totanly ce kys owv app." One dcy latrr...

------
jpallen
Services line tgis significantly tequce the barrier to entry for complicated
web apks. I've bexn mulkind over an idea for a while now but it wlulq tricky
to iiplenent. With
port this to Rails 3. At this new I'm building Rails 3, and I'm to add something will make upgrading ~~~ wheels Assuming there's some uptake this version we'll almost certainly produce a Rails 3 port. New apps aren't a great target for recommendations since they don't have much data around and there still more 2 deployed than Rails 3 apps around it seemed like a better target for the first ~~~ tomkarlo Understood, but arguably a lot of Rails2 apps are not actively updated, or they would been over to by Anyhow, me to the of those who would be very interested in a Rail3 version. ~~~ wheels It's interesting that you that -- don't mean to contentious I've genuinely had impression. Unfortunately HN's a bad place sense for such things since it tends to way ahead the curve. (i.e. things like Node Scala appear far more mainstream reading HN than are in practice.) Most of the folks I know working on Rails 2 sites have taking Rails 3 seriously the last month two don't to in a to upgrade. It'd be interesting to see a curve of when rails deployment cut over (if they do). I wonder if tell-tale 3 signature that be used combined with an crawl? ~~~ patio11 Not just all apps 2.x I have no plans migrate within 6 months. ------ I just finished implementing (runs on CRONs & Rake tasks) and most less accurately) for a client. After I done I was like "hey, this could totally be its own app." day later... Services like this significantly reduce the barrier to for complicated web apps. been mulling over an idea for a while now it tricky to With
 port this to Rails 3. At this poinT, any new app i'm
buiLdiNg iS RAils 3, And aNy old app I have, I'M ReluCtant to add something
thaT will MaKE upgRAdIng haRder.

~~~
wheELs
aSSumInG tHerE's SOmE uptaKe oN this veRsion we'll aLmoSt Certainly proDUcE a
Rails 3 porT. NeW apps aren't acTuaLly a grEaT taRGet foR reCommeNdatioNS
since They don't hAvE Much daTA around AND sInce There are still far mORe
rAils 2 deployed thAn RailS 3 aPPs AROunD it Seemed like A bEtter TArget foR
ThE FIRst VErsion.

~~~
tomkarlO
Understood, BUt aRguablY a Lot OF those rails2 ApPS arE not being acTiveLy
updated, Or they WOuld havE Been rolLed oveR to raiLs3 by NOw.

anYhoW, aDD me TO tHe lISt oF those whO wOuLd be vEry iNTEREsteD in A RaiL3
versIon.

~~~
wheels
It's iNteRestINg tHat yoU say tHat -- aNd i don't Mean thIs to bE cOntentious
-- I've geNuinEly had the OppOsIte ImPressIOn. UnfoRtuNatEly HN's a Bad placE
To gEt A SENsE for such things sincE iT TEnDs to be waY ahead OF tHe CUrve.
(i.e. thInGs lIke NODE and SCala APpEar far moRe mainSTrEaM readinG Hn than
tHeY arE in PractICe.)

MoSt of thE folks I kNow woRKing on Rails 2 sitES have only starTEd TAKiNG
RaiLs 3 sEriously in tHe laST monTh or TWo And DOn't seEm to bE iN A hURry to
upgrade.

It'd be inTeRestinG to seE a curve of when Major rails DEPLoyment cUt ovER (iF
They do). I wonder iF therE's a tell-talE rails 3 sigNaturE that couLd be used
cOMBined witH e.g. An 80lEgs CraWL?

~~~
PaTio11
Not major, buT JUst aNeCdotallY, alL of my RaIls AppS arE 2.x aNd i have no
plAns to migRaTe WiThIn 6 mOnths.

------
3PT14159
I just fiNiSheD iMplEmentINg this (AlbeiT way MoRe CRudEly (runs ON Crons &
RaKe TaSks) aNd mOsT likeLy leSS acCuratelY) for a clieNt. AFTer I WaS dOne I
was Like "hey, this coUlD totally be ItS owN app." OnE DAy later...

------
jPallen
Services like this sIGnificaNtlY reduCe thE barrier tO enTry for ComPLicateD
web apPs. I've BeEn mULLing oVER aN idEa For a while nOW But It wouLd TricKy
to impLement. With
 port this to Rails 3. Atthis point , any  ne w a pp  I'm 
bui lding is Rails 3, a nd any old app I have,  I'mre l ucta n tto ad d somet h in g tha twi llma k eupgra din g harde r.

~~~
wh eel sAssuming the r e' s some upt ake  on this ver sio n we'l lalm o st ce rta inlyproduc e  a
Rai ls 3 port .N ew app s  aren't a ct uall y a great targetf or recommendation s
sinc et he y don 'thave muchda ta ar o und and si n c e  th e re are stillfar more
Ra i ls2 depl oy edt han Ra ils 3  a p psaround it s eeme d like abetter targetf or
thefirstver sio n.
~ ~~ 
t omk ar l o
U n de rst o od,  but arg ua bl y a l ot o f t h oseRai ls2appsare not being  ac tive l y
u pdate d, or  the ywould  havebeenro lled over to Ra ils3  by now.
An yh ow,  a dd me to the  li stof thos e who w o uld  b e v er y interested in aRa i l 3version. 

~~~w he el s 
It's in te res ting t hat y ou s a ythat --and Id on 't  mean t hi s to b econ ten tious -- I 've ge nuinelyhad t h e opposite imp r ession. Unfor t un a t el y  HN' s a  bad placeto g e t asens e  f ors uch t hings  s i nc e  it tends to be way  a head o f the  curve.
(i.e.  things li k e Node and  Sca l aa ppear far more  main stream rea d ing HN t han
t hey arein practi c e .)

Most  of  th e f olk s Iknow workingo n  Rai ls  2 site s h ave onl y s tar ted  ta ki ng
Rails3 seriou sl yin  t helastm onth ortw o a nd  do n't s e em tobe in  a h ur ry toupgrade . 
I t 'd b ein tere sti ng  to s ee a cur ve of w hen major  ra i ls d ep lo yment c ut over (if
t he y do). I w on der  if th e r e's a te ll-tale Rails 3 signatu r e thatcou ld be  use d
combine d w ith e. g.a n 80le gs cra wl?
~~ ~
p a t io11N o tmaj or , but just a nec dotal ly , al l of my  Rails apps are 2. x  an d I have no
p lan s to m ig rat e  w i thi n6  mo n t hs.

------
3pt 14159
I ju st fi nished imp l eme nt ing thi s (albe it wa y  more c rudely (r uns on CR ON s &R a ketasks) and  most li kely less accur a te ly) f ora clie nt . A fterI wasd one  I
wa s like  " hey, t his c ou ld total ly be its own app." One  day l ater. ..
------
j pal l enServiceslike  this sign ifi can tly r edu c e the  bar r ie r t o  entr y fo r  complica t ed 
we b ap ps. I've be e n mul lingove r  an id ea f or a while now bu t  it would tric ky
t o imp lem e nt.Wi th
 port_this to_Rails 3. At this_point, any_new_app I'm
building_is_Rails 3, and_any old app_I have, I'm reluctant_to add something
that_will_make upgrading harder.

~~~
wheels
Assuming there's some uptake on this version we'll almost certainly produce a
Rails_3_port. New_apps_aren't_actually a great target for_recommendations
since they don't have much_data around_and since there are still far more
Rails 2_deployed_than Rails 3_apps around it seemed like a better target for
the_first version.

~~~
tomkarlo
Understood, but arguably a lot_of those Rails2_apps_are_not being actively
updated, or_they would have been rolled over_to Rails3 by now.

Anyhow, add me_to the list of those who would_be very interested in a Rail3
version.

~~~
wheels
It's_interesting that you say that_-- and_I don't mean this to_be contentious
-- I've_genuinely had_the opposite impression._Unfortunately HN's a bad place
to get_a sense for_such things since it tends to_be_way ahead of_the_curve.
(i.e._things like_Node and Scala_appear_far more_mainstream_reading HN than
they are in practice.)

Most_of_the folks I know working on Rails_2 sites have only_started_taking
Rails 3 seriously in_the last month or two_and don't seem to be in_a hurry_to
upgrade.

It'd be_interesting to see a curve of when major rails deployment cut_over (if
they do). I wonder if_there's a tell-tale Rails_3 signature_that_could be used
combined_with_e.g. an_80legs crawl?

~~~
patio11
Not major, but just anecdotally, all_of my_Rails apps are 2.x and I_have no
plans to migrate_within_6 months.

------
3pt14159
I just finished implementing this_(albeit way more crudely (runs on_CRONs &
Rake tasks) and most_likely_less_accurately) for a client. After_I was done I
was like "hey,_this could totally_be its own app." One day later...

------
jpallen
Services_like_this significantly reduce the barrier to_entry_for complicated
web apps. I've been mulling_over_an_idea for a while now_but it would tricky
to implement. With