What's the skinny guys? Is this an early April Fools joke, or the real deal?
> What's the skinny guys? Is this an early April Fools joke, or the
> real deal?
> I really hope that merb's naming scheme wins out.
> Application beats ApplicationController and before beats
I personally think Rails convention will win simply because there is
more code to change otherwise. But it does not look like a problem to
There are much more important things like making ActiveSupport monkey
patch less aggressive and perform better, make ORM finally pluggable,
> What I'm most curious about are the codebases. Is Merb itself becoming
> the foundation of Rails 3.0 or are the Merb guys bringing the Merb
> philosophy to the existing Rails codebase
It makes sense to move changes from a younger project to the more
I want to ask community members is to calm down a bit and believe that
newly formed rails-core-and-rails-more team can figure out a good way
to make Rails 3 shine. But roadmaps for merges like this one are not
done in one day.
I don't have any specific knowledge about either of the
implementations, but I'd like to push back on this a bit,
based on general software experience.
My impression is that the Merb core is smaller, cleaner,
and better documented than the Rails code. Adding Merb
code to Rails could therefore leave islands of clean code
in a sea of mud.
In contrast, if the Merb is used as the starting point
and folks like Ezra and Yehuda get to vet any additions,
I could believe that the result would be quite sanitary.
That said, however, I defer to their judgement...
My other concern is one of attitudes. The Merb camp has
a refreshingly user-centered attitude (where the user in
this case is the Merb developer). Basically, they act as
if their goal is to make the developer's life as easy as
possible. I haven't seen this in the Rails approach, to
date, so I worry that things could change for the worse:
"If man could be crossed with the cat it would
improve man, but it would deteriorate the cat."
-- Mark Twain
Technical editing and writing, programming, and web development
Wider industry adoption?
PS I use rails at work and merb at home. I don't have anything
personal against rails. Just sad to lose a choice. My bet is merb
will eventually resurrect itself sometime before or after Rails 3.0.
On Dec 24, 2008, at 3:03 am, Justin Reagor wrote:
> Unless Rails 2 is trashed and completely replaced by Merb. In which
> case, why does Rails get the title and tech just handed to it?
> Because we need the logo rights?
Rails 3 = Merb 2 + a transitional Rails compatibility layer, right?
At least I hope that is the intention, or there will very soon be
hundreds, if not thousands, of upset, disillusioned Merb developers
> 1) What is the process going to be like for adapting existing Merb
> plugins to the hybrid framework?
Right now all the discussions involve keeping compatibility as much as
we can. It is sometimes good, sometimes bad. We will see how it goes
in the future.
> 2) Can slices be used in Rails 3? And if so wow will slices have to
> be changed to fit in?
Slices/engines/you name it will be one of the crown jewels for Rails
3.0. Most ideas I heard of so far come from what slices taught us
through Merb's evolution.
> 3) Will there be a performance hit for using legacy rails plugins?
It depends on how your plugin is written. No framework can speed up
slow code that comes from 3rd parties.
No one knows. Things change. Wait for it to mature and then see what
comes out. I wouldn't be too worried about the technical details
anyway since there's a bunch of competent people from the merb camp
and a bunch of competent people from the rails camp working on the
same project together. Generally (in a logical world) the sum of two
positives is positive.
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?
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 <mikhailo...@gmail.com> wrote:
What you think about new logo?
On Dec 24, 4:21 pm, Samo Korosec <smoof...@gmail.com> wrote:
> Hey, at least DHH ends his "adressing the concerned 4%" post at
> "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!