Or Shiva3D?
Dart's biggest competitive advantage is that it has teams building compilers, VMs, libraries, apps and tools. It is not just about syntax sugar. It is also about better debugging and collaborating, improved development…
The bad thing is bashing without trying to understanding the problem they are trying to solve and the audience they are targeting.
It seems that what you ended up doing is, in fact, reimplementing things that were implemented zillions of times before. Am I wrong or the Pump middleware doesn't work for any WSGI app? If it had followed the WSGI…
It is ironic that they mention "don't have to reinvent the wheel" in that page.
I have the impression that experienced Python programmers don't feel comfortable with web2py's controversial (some would call "unpythonic") approaches, like automatic imports or the use or exec.
I think you're confusing the general idea of cursors with datastore cursors, which require a query and can't be created "per request", but "per query". See: http://code.google.com/appengine/docs/java/datastore/queries...
Does the web2py database abstraction layer support datastore transactions and query cursors? Or what datastore features it doesn't support? (apparently the documentation doesn't mention any datastore feature it doesn't…
Thanks for the mention! (I'm the webapp2 author). A big advantage of webapp2 is that you can use existing (and probably future) SDK libraries without adaptation. Many App Engine services (blobstore, mail handler,…
Or Shiva3D?
Dart's biggest competitive advantage is that it has teams building compilers, VMs, libraries, apps and tools. It is not just about syntax sugar. It is also about better debugging and collaborating, improved development…
The bad thing is bashing without trying to understanding the problem they are trying to solve and the audience they are targeting.
It seems that what you ended up doing is, in fact, reimplementing things that were implemented zillions of times before. Am I wrong or the Pump middleware doesn't work for any WSGI app? If it had followed the WSGI…
It is ironic that they mention "don't have to reinvent the wheel" in that page.
I have the impression that experienced Python programmers don't feel comfortable with web2py's controversial (some would call "unpythonic") approaches, like automatic imports or the use or exec.
I think you're confusing the general idea of cursors with datastore cursors, which require a query and can't be created "per request", but "per query". See: http://code.google.com/appengine/docs/java/datastore/queries...
Does the web2py database abstraction layer support datastore transactions and query cursors? Or what datastore features it doesn't support? (apparently the documentation doesn't mention any datastore feature it doesn't…
Thanks for the mention! (I'm the webapp2 author). A big advantage of webapp2 is that you can use existing (and probably future) SDK libraries without adaptation. Many App Engine services (blobstore, mail handler,…