I thought I explained that perfectly well - it may be as good, but it has not the length and bredth of track record.
We can do things; we can do things quickly; we can show how you would do things; sometimes we find that things you would want to do just a little different aren't so easy to do, because we hadn't run into, thought of. or otherwise encourntered that. Sometimes people want to do things different "just because they want to test if they can", but sometimes people want to do things moderately differently because they are sitting with a client, want to tweak the prototype for the client to match what he is asking for (and may or may not later suggest a better / different / more efficient approach). If stage 0 is an idea; stage 1 an implementation that works for me; stage 2 an implementation I can show others how to use stage 3 an implementation that can adapt to the needs of the real world under commercial demands stage 4 is wide use across more than one industry stage 5 is evolution and standardization, and adoption by major institutions stage 6 is a standard... Then django (regardless of technical / age / etc. arguments) is firm stage 4, having entered stage 5 (by virtue of GAE); Most other frameworks (and not just python ones, and including ones with large backing by corporations) are lucky if they make it into stage 3, and rarely make it to stage 4 (things change too much in the internet - and we are embarking on yet another wave of major changes, mobile and rich clients being the _least_ of them!) django is unusual in this regard, and - even as you can argue that things can be made better, you cannot deny this is the state of django - quite an accomplishment, and a testament to the power of media (e.g. news industry), and the effects of surviving the demands of that industry. web2py, in my humble and simplistic painting of the scenario here, is firmly in stage two, poised at the brink of "entering" stage 3 (which it has not done yet in a long-term, varied, consistent way, without saying anything about if it can or can't... what the forces are propelling it, what are the forces resisting it at this moment). What I said was "go yonder into the stage 3 world, and bring lots of feedback into these here forums". When that has happened over the next year(s), then I'll talk about how we're poised to enter stage 4. In the meantime, the quickest way to get noticed by the likes of google, guido is to continue to do useful things, continue to be part of conferences, and perhaps push some of the early stage 3 efforts into wide and heavy use _on_ gae. This will get early attention. All else is, in effect, premature. Happy designing! - Yarko On Sun, Jul 5, 2009 at 8:23 PM, weheh <[email protected]> wrote: > > Agreed with Yarko that until and unless web2py is as effective with > Google Apps as Django, then I would hold off any petitioning. However, > if it is as good, then I don't understand why Google would necessarily > show such a clear bias towards Django on the Google Apps info page. In > addition, assuming there are web2py Google apps to point at (I intend > to develop one) then in that case a petition would be in order, > especially if it came from the community of which I am a part. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
