Jump to content

Talk:Web2py

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Joebarnhart (talk | contribs) at 17:30, 20 July 2009. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Does anyone have any negatives to list about this framework? --RobKohr (talk) 23:46, 21 July 2008 (UTC)[reply]

Given nobody uses it (apart from its author), probably not. —Preceding unsigned comment added by 93.4.223.206 (talk) 08:55, 1 April 2009 (UTC)[reply]

It must be said that although the software is GPL, there is no free manual, so your deemed to buy the manual to use it! --marc (talk) 17:55, 28 September 2008 (UTC)[reply]

A small correction - plenty of free documentation is available on the site, the 'official manual' which does cost money is a (useful, but not necessary) academic publishing. —Preceding unsigned comment added by 93.86.78.92 (talk) 21:34, 27 March 2009 (UTC)[reply]

This web framework is very nicely designed. It is small enough to fit on a memory stick and approachable by anyone know knows Python. That said, I have to admit I'm looking elsewhere for a framework now after attempting my first web2py application. The problems:

  • Lack of documentation. The book is very good, by its very nature the book is out of date practically the moment it is published. Other resources include the GoogleGroups forum, the FAQ, etc. but there is a serious need of something like a Wiki to capture and organize the docs.
  • Lack of focus. The need for a wiki was discussed in the forum but instead of using a best-of-class wiki engine it was decided to build the wiki from the ground up in Web2Py. Of course, the developers were already busy trying to develop the platform so the web2py-wiki failed to materialize. The project team gets distracted by issues such as creating an organization for certifying web developers and competing with the likes of IBM. It gives the impression that the project has some serious ADD issues.
  • Control issues. The project was released under a modified GPL instead of a more permissive license such as MIT. The documentation is done only by the platform creator. (Instead of doing a wiki it was decided to use a version control system which restricts write access.) A developers list was set up recently but write access was restricted. Everywhere you turn there seems to be a big emphasis on control.
  • Emphasis on "enterprise". The project leader believes that his platform is for the "enterprise" which I believe is opposite of its true strengths. I don't think PepsiCo would care if their entire web delivery platform fits on a 1G memory stick. Web2py's true strength is that it can deliver a full-function web platform on a very small -- and portable -- footprint. I think web2py could be used by hobbyists, students, clubs and organization, churches, HOAs, etc. It doesn't need to be "enterprise" to be successful. Its success won't come from the companies who make up the Fortune 100.

The ultimate result is lack of productivity in using the framework. So much time is spent pouring through the source code to answer your own questions that it really gets in the way. Better docs, consistent focus, less restrictive control over everything, and emphasizing web2py's true strengths would make a huge difference. I'll look at it again after I pursue some alternatives in the interim.

Joebarnhart (talk) 21:25, 19 July 2009 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Web2py&oldid=303167823"