----- all the rest of this is smack-dab peachy: I'll remind you of one thing - there was a website, guy from NOAA I think it was - that showed all the frameworks that claimed to have something; he tried building something simple with them and uncovered all the flaws and gotchas and try to say "here's what I would (wouldn't) want to build with".... most things just took a long time... -----
Actually, it was a guy from JPL as I recall. In fact, watching his screencast is exactly what got me started looking at frameworks and CMSs. One thing led to the next and I found Django. And then I watched a video of one of Django's developers and he said something like this: "... Django's templataing language is different from python because it's made for page designers. Page designers don't write programs and programmers don't design pages." That is exactly what lost me for Django. Then I found web2py and the rest is history. I agree wholeheartedly with MDP's observation of the 80:20 rule. However, I find that web2py is an exception. On my first web2py app I probably used 90-95% of the features of web2py. On the next app, it will be 100%. Interestingly, my plate will be clean AND my appetite sated. There is nothing extraneous in web2py that I can discern. Web2py's niche is that one person of reasonable skill can develop a sophisticated enterprise web application in minimal time with minimal effort. This is because of its 3Cs: consistency, completeness, and conciseness. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
