Interesting development. This seems to address the common criticisms of web2py, which aren't an issue for me but surely deter others.
On Friday, November 30, 2012 3:51:20 AM UTC+11, LightDot wrote: > > Some valid and interesting questions can get unanswered, slip below > the radar, that's bound to happen everywhere. I have a feeling that > web2py community is very active when compared to some others, taking > the number of members into account. It would be interesting to put > some numbers behind this and prove one way or another, but alas, I > don't really have the time... :/ > > My personal observations are that unanswered questions are often > either a) accompanied by complex, long examples of code, which many > readers don't have time to decipher; b) answered many times before or > so general, that they aren't web2py specific at all (ie. general css > or html questions); c) very specific, with sparse information about > the problem itself (such as individual web server configurations, > etc.). I might be wrong though, as I naturally don't read > everything... > > Regards, > Ales > > > On Thu, Nov 29, 2012 at 3:25 PM, Jim S <j...@qlf.com <javascript:>> > wrote: > > +1 to what Peter said. > > > > > > On Thursday, November 29, 2012 4:06:30 AM UTC-6, peter wrote: > >> > >> In my experience, and what I have seen from following the threads, the > >> norm is for questions to be answered very well and very quickly. One of > the > >> many pleasures of using Web2py is the responsiveness of the users > group. > >> There might be the odd exception to this, but this is unusual I > believe. So > >> sorry if you had a bad exprience Daniele, but I do not think most users > find > >> this. > >> Peter > >> > >> > >> On Thursday, 29 November 2012 01:14:52 UTC, Daniele wrote: > >>> > >>> I really believe web2py will indeed become the "rails for python" as > >>> someone mentioned. Actually, I believe it's much better, easier to use > and > >>> comprehend, and more pleasant to develop in. > >>> > >>> That said, I agree web2py needs to reach a critical mass of users > because > >>> as of now, it's too hard to get the support to even simple answers, > which > >>> sometime require days to be answered on google groups. A much wider > user > >>> base would rapidly solve this problem quite naturally. I think the > solution > >>> to this would be word of mouth: more users need to use web2py and > spread the > >>> word of how good it is by mere word of mouth. It's possible, I believe > the > >>> project can really outshine all the other python web frameworks. > >>> > >>> On Tuesday, November 27, 2012 4:39:06 AM UTC, User wrote: > >>>> > >>>> I noticed a thread over in web2py-developers web3py - important! > which > >>>> was exciting to read. I've flirted with web2py and there's a lot > that I > >>>> like about it. For some reason I find web2py exciting whereas django > >>>> doesn't provide that. I've used Yii on the php side which is great > >>>> framework as far as php goes and asp.net mvc which is great as well. > I'd > >>>> love to work with python but the main thing making me hesitate with > web2py > >>>> is critical mass. > >>>> > >>>> It seems like it wouldn't be hard for web2py to really dominate the > >>>> python web framework space if some of the core criticisms were > addressed. > >>>> I'm not fully up to speed on what they are but I usually hear about > unit > >>>> testing and global variables. It feels like there is a roadblock > preventing > >>>> the project from skyrocketing. Python needs a rails. I understand > that the > >>>> design decisions are by choice with pros and cons. > >>>> > >>>> My questions are: > >>>> 1. Will web3py likely address these often repeated core criticisms? > (I > >>>> saw point 5 from the thread linked to above: "5) No more global > environment. > >>>> Apps will do "from web3py import *" (see below)") > >>>> 2. The developer thread is over in the developers section. Will you > >>>> have a more open forum for users (as opposed to developers) to have > input on > >>>> web3py? > >>>> > >>>> > > > > -- > > > > > > > --
