> Hello! > > I'm starting with python & web2py and yesterday visited > Hello, > > I'm starting with Python & Web2Py and yesterday visited one python-related > project channel where I mentioned web2py and as the consequence I was > quickly > advised to abandon it due to 'non-Pythonic' etc. > > This is not the first time I hear people criticise web2py due to, amongst > other > things, breaking "Explicit is better than implicit." principle alothough > Massimo nicely explains it in the introduction of web2py book. > > I played for sometime with the Haskell, but eventuall abandon it due to > not > being pragmatic enough for daily use (e.g. all GUI bindings are maintained > by > few people only). The same situation was/is with D. > > Now, I see Python as very pragmatic language, with lot of 'batteries > included' > and very suitable for all kinds of tasks, so I wonder waht is the real > reason > of web2py criticism: > > a) stubborness of (python) people to see that "Explicit is better than > implicit." is not engraved in stone and can be violated to keep DRY, > > b) envy of web2py's success > > c) something else? > > As far as I'm concerned, I do not care much 'cause I'm accustomed to do > things > which are not mainstream, but just curios what do you think? > >
If you want an adivse, do not trust those kind of people. Whoever claim itself a technology-guy and has fear of diversity, or 'non-ortodox' approaches should probably start looking in other areas... If someone blaim a project because it does not work, it has horrible documentation or the author likes killing kitten, this is good. But blaming a project for not being loyal to some concept is silly. It looks like more a religious approach than a techy one. Web2py works (and most of the time it simply works thanks to its design), it is well documented and AFAIK Massimo does not like killing kittens. But yes, if your priest.py does not approve it, do not use it :P -- Roberto De Ioris http://unbit.it
