Dear friends, sorry for intruding but Robert makes a good point and I would like to answer that.
On May 7, 9:46 am, Robert Walker <[email protected]> wrote: > > web2py in particular seems very interesting because it sounds like it > > incorporates many ideas from ROR but may be easier to set up, learn, > > develop with, and deploy. Does anyone have any experience with both > > ROR and web2py? > > Why use something that "incorporates many ideas from ROR" when you can use > the framework that inspired them? Rails is an excellent framework. I am a Python programmer but I would still pick Rails over most of the Python frameworks, both because of its design and because of how professionally it is evolving. Whether Anthony choose Rails, Django or web2py, I think it will be a huge improvement over PHP. Yet the comment below deserves a response because it is based on a misconception. web2py does not attempt to copy Rails and it is not mix and match of features that you can find on other frameworks. Here are some of its unique features: web2py does not require installation and has no configuration files; it has a one click button that turns apps into bytecode compiled apps that can be distributed in closed source; the web2py Database Abstraction Layer supports 10 different back-ends and it is the only DAL to support the Google App Engine (that means the same exact code runs on GAE and Oracle); It comes with a web based IDE that can be used for development, debugging, testing, deployment, internationalization/translation and maintenance (all in the browser); web2py helpers provide a server-side representation of the DOM and than be used to build generate XML/HTML programmatically without manipulating strings; web2py migrations do not require writing migration files, are automatic based changes in the models vs what is in the database; it has a different system for generating forms from models; web2py promise backward compatibility to the users and this was not broken since 2007 (even if lots of new features have been added). The two main features that web2py got from Rails (in striking contrast with all of the other Python web frameworks) are: it gives precedence to "convention over configuration" over "explicit is better than implicit" (a Python motto, this pissed off a lot of python users); full Python in templates (in your case full Ruby in templates), while Django for example has its own template language. Another comment was: > One does not learn to fly airplanes by becoming a > test pilot for experimental aircraft. True. web2py is 4-5 years younger than Rails and it has smaller number of users. Yet it is not an experimental product. It is 3 years old and counts >50 contributors and >1800 registered users. Most users use it for intranet applications which unfortunately you do not see. Anyway, Rails came first and it was a great experience to learn from it. Thanks Rails. Massimo -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
