Hello On Tue, Jan 6, 2009 at 7:36 PM, Julian Leviston <[email protected]> wrote: > 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.
Not sure if this was directed in my direction, but for the record, my comments about the fast changing landscape are from before the merger was announced. > 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. I'm not sure any of the plugins will make it across unscathed. That is, I'm sure there will need to be some changes, assuming that merb keeps its optimum architecture. I think the real advantage will be more developers, and hopefully a few gems (plugins) will be well vetted, bubble to the top and actually useful. I used a few plugins when running rails, but found that most needed tweaking or customization and soon came to the conclusion it was faster to write my own. Jim > Julian. -- Jim Freeze --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
