Femto Zheng wrote in post #996564: > Hello all, because most of php's application is feature rich than > rails's existing offer, > like say, crm solutions, sugarcrm, > I know rails have similar offering,( fat_free_crm), but unfornately, > this is really far > from the feature sugarcrm offers, > sugarcrm has been developed since 2004, all 7 years, and has been > funded > $2 million in venture capital, I just don't think anyone could port > that easily in > a short time frame. > > for hand-rewritten the php's application, well, that's at least > theoretically, > I've done that before, that's quite time-consuming and error-prone. >
Possibly time-consuming, yes. Error-prone depends on the tests that are in place... But the generated Ruby you show above would cause most Rubyists to flee. If the entire application is translated with that amount of syntactic noise, what is your maintenance path? Edit the original php application, then translate again?!? I'm not knocking your accomplishment (Lord knows I've written code that writes some awfully ugly code), but there a wide gap between syntactic/semantic correctness and syntactic/semantic "elegance", and I think the "elegance" attribute is what has drawn many people to Ruby. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.