On Wed, Dec 24, 2008 at 10:52 AM, Rue the Ghetto <[email protected]>wrote:
> While I do feel like this could be a good thing, I also feel like the rug > has been pulled out from under me. > As the lead developer for a small Ruby web shop, I was able to push Merb > into a couple interesting commercial projects. We have projects dating back > to version 0.4.X. In the Spring, I built a green PR site for > Whirlpool/Method that calculated the water quantity and usage of a user's > household. It was so calculation and database heavy that it really shined > under Merb. Sadly the project died after it was built for lack of marketing > funding. > > Afterwards, we built greenwala.com. That is when the decision to use Merb > turned into an investment in the framework. We had an excellent CMS built in > Rails that met all our client's needs, but decided to rebuild in Merb > because our company believed in Merb's speed, modularity and philosophy. We > eschewed the numerous rails plugins that would have made our life so much > easier, because we wanted to build a new set of tools for Merb. We struggled > with openid, pagination, and facebook, using a much smaller pool of > competent developers. We had plans to extract our CMS and possibly the > social network into a slice. Just recently I started extracting the generic > parts of facebooker into a gem to open source. That way there could be an > adjunct rails/merb/mack/whatever gem that worked with framework specific > items. After the announcement, doing that kind of work seems foolish. > > Although I haven't made significant contributions to datamapper or Merb, I > have been an ardent Merb user and an evangelist for this new little > framework that could. Perhaps I flatter myself to think that Merb owes > people like me, early adopters, some notice or input before this kind of > change. > > I have a few questions for the new core team that will help me figure out > where to invest my coding and open source time: > > 1) What is the process going to be like for adapting existing Merb plugins > to the hybrid framework? > The current plans involve porting plugins like merb-helpers to Rails3, and providing transitional releases (and probably a transitional plugin for Rails3) to aid in the transition. How does that sound? > 2) Can slices be used in Rails 3? And if so wow will slices have to be > changed to fit in? > 3) Will there be a performance hit for using legacy rails plugins? > > Thanks for listening ... really! > > On Wed, Dec 24, 2008 at 2:49 AM, mikhailov <[email protected]>wrote: > >> >> What you think about new logo? >> http://www.railsgeek.com/2008/12/23/rails-3-rails-and-merb-merge >> >> On Dec 24, 4:21 pm, Samo Korosec <[email protected]> wrote: >> > Hey, at least DHH ends his "adressing the concerned 4%" post at >> > >> > http://www.loudthinking.com/posts/36-work-on-what-you-use-and-share-t. >> .. >> > >> > classy; >> > >> > "So kumbaja motherfuckers and merry christmas!" >> > >> > First there's an annoucement that feels like a slap in the face to the >> > merb community and then we get a nice taste of what's coming, yay! >> >> >> > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
