At 03:55 +0300 12/24/08, Michael Klishin wrote: > It makes sense to move changes from a younger project > to the more mature one.
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 -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume [email protected] http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
