For me, Rails 3 is just too much of an unknown quantity at the moment to do anything too significant with it yet. At some point soon I'm hoping to take one project and try to convert it to use the latest Rails from github just to try and track what's going on and evaluate whether it's likely to become my platform of choice in the future. But it's too early for me to jump back to Rails completely at this point.
Actually if anyone does do this (some exploratory testing of the latest rails from a merb perspective), it would be good to see some notes here or on a blog somewhere about what they learn. On Nov 23, 5:31 am, Chris Hoeppner <[email protected]> wrote: > I for one will continue to use merb while it is bearable, and this > includes new projects. I have just recently started one. > > chris wrote: > > With Rails 3 / Merb 2 not too far away, which framework would make the > > most sense to start a project in right now, in regards to updates to > > move to rails 3? (this is assuming that one chooses to use > > activerecord as the orm). I guess this is also a question to which > > framework will the next version resemble more. > > > Thanks. > > > -- > > > You received this message because you are subscribed to the Google Groups > > "merb" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/merb?hl=. -- You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/merb?hl=.
