This whole issue amuses me greatly. Developers find it seemingly easy to abstract patterns from code. Yet, when it comes to doing something as comparatively conceptually simple as thinking about the development of two web frameworks converging where the positives from ALL frameworks get carried over (including no- bloat), they cannot grasp it.
From Merb's point of view, Merb gets all the benefit of code that has been built from real-use scenarios to address real-user problems, but keeps all of its modularity and keeps its small footprint and its speed. From Rails' point of view, Rails' internals get a total work over, and become tight, small and modular, exactly as Merb's are. They end up at the same point. Debating it is ridiculous - it's simply a naming issue - but as we all (SHOULD) know, a thing is the same thing if you call it a different name. I tend to think that a lot of people use Merb because of its IMAGE as the "small underdog which is more powerful" rather than the actual code. If you renamed Rails 3 to Merb 3, then I'd say that pretty much ALL Merb people would be happy. I'd wager it's simply a naming issue at the root of it. Ironic, isn't it? ;-) Julian. On 07/01/2009, at 9:41 AM, Yehuda Katz wrote: > That's a pretty simplistic view of the situation. I think you're > overemphasizing the (rather minor, imho) differences in your mind > and underemphasizing the philosophical sameness. I'm not downplaying > the annoyance of having to change things, but saying that the > "learning" is not transferrable is really just not true. > > -- Yehuda > > On Tue, Jan 6, 2009 at 2:16 PM, Jim Freeze <[email protected]> > wrote: > > On Tue, Jan 6, 2009 at 3:27 PM, CRS <[email protected]> wrote: > >> Merb is merging, which would be easier/better to go from merb to > Rails > >> 3.0, or from Rails 2.0 to Rails 3.0? > > > > I've been into Merb just over a month after coming from Rails. > From what > > I've heard, you can go with you're most comfortable with. It's > gonna' be > > "footprints in the sand" > > (http://www.frtommylane.com/stories/God/protector/footprints.htm) > on both > > sides, Rails or Merb. > > > > Me? I'm very confident about letting Merb carry me. > > I'm confident I'm going to be writing my own web framework sometime in > the future. > > Seems like if a web project takes more than 2 months, the following > project is using a new framework, so the learning that you can carry > on to the next project is very limited. > > > -- > Jim Freeze > > > > > > -- > 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 -~----------~----~----~----~------~----~------~--~---
