I usually fall on the libraries camp when it comes to libraries vs frameworks.
So the extent to which webpy can remain a minimalistic framework that someone can wrap around their head in a day or two, and then pick and choose as they please, the better it will be for me. On Thu, Mar 26, 2015 at 3:02 PM, tensio <[email protected]> wrote: > First of all, I think it is great that we finally start the discussion about > the future of web.py > > So let's go: > > PROs: > The Simplicity: Web.py is simple to use, especially for beginners BUT for > experts it has all the things needed to develop stuff yourself. > Database Module: It's extremly simple to use > > CONs: > Further Development: The Web changes so should web.py > > I would love to see: > Memcached session module (there are some out there, we should add it to > master) > Google App Engine && Amazon Web Services Integration (maybe even heroku) > (they have specific needs for saving stuff and database handling) > > Also I think the Templating System is quite good. But I agree with Primoz: : > something like $endfor would make it even easier to use > Oh and I think that the forms plugin could need some work. As custom css is > quite hard to use (Bootstrap) > Yannik > > Am Sonntag, 15. März 2015 19:06:34 UTC+1 schrieb Anand: >> >> Hi, >> >> Before we discuss about the roadmap, I would like to hear from all of you >> about what are the things that you like, don't like and hate about web.py. >> Please also add your wish list of features. >> >> I hope that'll give us change to think and plan a better roadmap. >> >> Let me start with myself. >> >> GOOD >> >> * The best part of web.py it its simplicity. There are not many layers of >> abstractions and it is very easy to understand how things work behind the >> scene. >> * The db module >> * simple URL dispatching >> >> NOT SO GOOD >> * The template module - i think using indentation to identify blocks was a >> bad idea. I had trouble with it lot many times. >> >> BAD >> >> * There are not many third-party libraries to use with web.py. I would >> like to see more such libraries. >> * documentation - we need more documentation. >> >> UGLY >> * forms - the forms library is not as elegant as it should be. Declaring >> an object and calling to to create a copy is an ugly hack. >> * sessions - sessions got into web.py as part of google summer of code and >> I was never happy with its quality. Some one tried to do some improvements, >> but think it shouldn't have come to web.py at all. >> * development & releases - I've been very bad at maintaining and handling >> the releases in time. Hope I'll get better at it and expecting more people >> to contribute. >> >> WISH LIST >> * Python 3 support >> * can we do asyncio with web.py? >> >> Anand > > -- > You received this message because you are subscribed to the Google Groups > "web.py" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/webpy. > For more options, visit https://groups.google.com/d/optout. -- A data bank of highly qualified professionals in Kenya - https://dumaworks.com "The difference between theory and practice tends to be very small in theory, but in practice it is very large indeed." - Anon https://github.com/krmboya -- You received this message because you are subscribed to the Google Groups "web.py" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/webpy. For more options, visit https://groups.google.com/d/optout.
