Web2py Update

[Maurice Waka]

Hi

I have been using web2py for about 1 yr now. I love it. I recently came acros this crazy article about web2py advantages and disadvantages.

My question is that have, these disadvantages been addressed since 6 yrs ago in your updates? 

Am working on and app and would love to launch it soon, in web2py and I dont want programmers to come and discredit my work.

Here is the link: http://ahmedsoliman.com/2010/07/29/the-good-and-bad-about-web2py/

Kind regards

[Niphlod]

honestly you can find it yourself, but for the sake of recaps:

- small or none support for application's unittesting. up until now there have been a few experiments but no one landed in the code

- routes_onerror can be used to cook something that will display the error right away, and I'm not so sure it'll work fine but there was an extension for google chrome or firefox that opened errors right away. That being said nobody is telling that the admin app can't be improved, it's an app and totally customizable

- DAL is certainly improved in 6 years but still it won't ever be an ORM. That's the whole point of choosing a DAL over an ORM

- we can't faster IDE adoption but there are a few that work fine with a little trick (web2pyslices holds the recipe)

- web2py is completely multiprocess-aware. I'm not a big user of other frameworks but they smell less multiprocess-friendly than web2py (e.g. the cache and sessions). Because of those choices it's probably a little slower in single-process performances but nowadays production always requires multiple processes.

[Maurice Waka]

Thanks@Niphlod

--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to a topic in the Google Groups "web2py-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/web2py/Ol4YRkIsuew/unsubscribe.
To unsubscribe from this group and all its topics, send an email to web2py+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ron Chatterjee]

You forgot to mention explicit vs. implicit Niphlod but pretty much you sum it up well. One thing I didn't understand is:

"DAL is certainly improved in 6 years but still it won't ever be an ORM"

In other words, ORM is better than DAL?  If that's the case, someone can also use sqlalchemy like they can use with django. Am I correct? 

[Marin Pranjić]

On Sun, Feb 7, 2016 at 4:49 PM, Ron Chatterjee <achatte...@gmail.com> wrote:

You forgot to mention explicit vs. implicit Niphlod but pretty much you sum it up well. One thing I didn't understand is:

"DAL is certainly improved in 6 years but still it won't ever be an ORM"

In other words, ORM is better than DAL?  If that's the case, someone can also use sqlalchemy like they can use with django. Am I correct? 

No, it doesn't mean ORM is better. It just means they are different.

Some people like DAL more, some like ORM.

And sure, you can use sqlalchemy if you prefer an ORM.

Marin

 

You received this message because you are subscribed to the Google Groups "web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py+un...@googlegroups.com.

[Ron Chatterjee]

So in a way, ORM is supported. Okay, next...it says lot about unit testing. And some I do agree. Some of web2py error reporting is hard to figure out and it doesn't get very specific about exactly where the issue is (not criticizing but constructively put). Having said that there is a test module in the controller. Right? I haven't really played a lot with it. But what's the difference between unit test that you with django and other framework and the test in the controller module?