I'm not at home but I'll also reply later on today or tomorrow. - Matt
Sent from my iPhone On Jun 28, 2009, at 13:42, Yehuda Katz <[email protected]> wrote: > I'm going to take the time this weekend to thoughtfully respond to > this thread. With regard to the book, I expected that people > received an email from Manning explaining that the book has been > switched to Rails 3 in Action, which we are currently working on. > Unfortunately, since Rails 3 was up in the air as we were working on > it, it was hard to get started without having to radically change > the book as we moved forward. > > The idea of the Rails 3 in Action book is to cater to folks who are > interested in configuration their framework and learning the power > of the internals. So it won't be a beginner book, but it should be > everyone's second Rails book. I hope that helped answer your question. > > -- Yehuda > > On Sun, Jun 28, 2009 at 11:32 AM, Alistair Holt <[email protected] > > wrote: > > I bought the book too which does seem to have died a long time ago. > Surely Manning should be refunding their customers for buying a book > which it looks like is never going to be produced. > > On Jun 28, 5:39 pm, Julian Leviston <[email protected]> wrote: > > Yeah I'm pretty crapped off that the book that I paid for is > > apparently not coming from manning any more... and manning don't > reply > > to my emails. > > > > Julian. > > > > On 29/06/2009, at 2:24 AM, scottmotte wrote: > > > > > > > > > > > > > I'd would agree with Ezra that Merb is solid. I've built 3 > production > > > apps and working on a fourth. > > > > > However, even though Merb was solid, there was a lot of good stuff > > > planned for Merb 1.1 back on March 2nd, 2009. (but these weren't > > > promises just hopes) > > > - ruby 1.9 compatibility > > > - namespaced applications > > > - active orm > > > - run_later > > > - thor improvements > > > > > There was the impression/promise that Merb apps would provide a > > > migration path to Rails 3. That's probably my biggest concern > right > > > now. > > > > > Additionally, I'm still in the camp that it was a mistake to go to > > > Rails. It's been months of refactoring work for Yehuda - the > majority > > > of which was already a core part of merb it seems to me. And I > know > > > for a fact Yehuda has been very very busy. He deserves a medal for > > > taking on that code. You've seen his blog posts. Holy cow it's a > ton > > > of work refactoring rails. I think the Merb/Rails framework > would have > > > been quite further along if half the effort in refactoring rails > was > > > put towards Merb. > > > > > Having said all that, these are just my opinions. I haven't > > > contributed any code, and these guys know better than a non- > committer > > > like me. I've had the pleasure of meeting Matt, and I can say > that we > > > are lucky as a community to have such smart and giving dudes - > Yehuda, > > > Matt, Carl, Ezra and others. > > > > > On Jun 27, 11:07 pm, Nicholas Orr <[email protected]> wrote: > > >> Only thing I'm keen for is the run_later fixes for using with > > >> passenger... > > >> Since I only have one app that needs run_later in production and > > >> that is > > >> only for updating something once a month. I simply spool up a > thin > > >> instance > > >> on another port and update. Shut it down after it is done and I'm > > >> on my way. > > > > >> I've nearly finished a 2nd production merb app and everything is > > >> great :) > > > > >> All the funky stuff coming in the router would be "nice to > have" - > > >> it is not > > >> like I need them or my app wont work... > > > > >> Merb right now works really well and is very flexible. I say > kudos > > >> to the > > >> merb dev team and thanks for a solid framework that lets me get > on > > >> with what > > >> I want to do ;) > > > > >> Nick > > > > >> On Sun, Jun 28, 2009 at 1:51 PM, Ezra Zygmuntowicz > > >> <[email protected]>wrote: > > > > >>> On Jun 27, 2009, at 8:34 PM, MyMerb wrote: > > > > >>>> Hi, > > > > >>> I'd like to chime in and say that I am still happily > > >>> building apps > > >>> with merb,http://engineyard.com/soloisbuilt on merb. I don't > find > > >>> that there is anything I'm missing or that there are any > features or > > >>> major bugs stopping me from building apps with merb. > > > > >>> If merb works for you then use it, it is very stable and > > >>> runs well > > >>> in > > >>> production. If you need the newest shiniest features all the > time > > >>> then > > >>> rails is probably getting more love these days and may be a > better > > >>> option for you. > > > > >>> I'll let Yehuda and Matt chime in on the other questions > > >>> specifically > > >>> but I just wanted to say that merb is solid as is, it works > and runs > > >>> very well in production. I think merb is kind of feature > complete > > >>> and > > >>> extensible enough that you can build whatever you want with it > as a > > >>> solid foundation. > > > > >>> Cheers- > > >>> Ezra (happy merb user) > > > > > > -- > Yehuda Katz > Developer | Engine Yard > (ph) 718.877.1325 > > > --~--~---------~--~----~------------~-------~--~----~ 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=en -~----------~----~----~----~------~----~------~--~---
