I understand what you are trying to say but when you say "no one is
using web2py" gives people the wrong impression and not the correct
one. It is not fair to member of this community who use web2py.

You should also assume that there are lots of people on this list who
are considering web2py but have not yet made their mind about it.

As you pointed out Pycon 2009 used web2py to register 800 users and
handled thousands of monetary transactions.
http://www.klasproducts.com/ uses web2py to sell hundreds of products
http://www.spinyc.com/ uses web2py in their intranet
http://www.whitepeaksoftware.com/  uses web2py for their web site
http://diarywiz.com/ is powered by web2py

There are just some of those we know about and choose to advertise
what they do.

Of course more people will come out eventually. As I said most of the
work is done on intranet apps.

There is no question that Django is more popular and Drupal is
probably much more popular than web2py. They have been around longer,
came first and had more time to build a community. Moreover Drupal is
a designed to build CMS therefore apps made with Drupal are naturally
publicly available.

I do not think discussion about how popular we are vs how popular they
are is healthy. Moreover despite what some people think I do not care
much about it. I would like the discussion to focus more on what we do
better (feature wise), what they do better, what can we do to improve
our features, what can we do to promote web2py features.

Some people are not interested in features as are only interested in
learning the system that will give them the highest chance of getting
hired. Some people are interested in features as a way to get the job
done better and quicker. I am working for this second class of users.
I am interested in building a community for these people.

Massimo



On Jul 6, 2:18 pm, Yarko Tymciurak <[email protected]> wrote:
> Hey weheh -
>
> On Mon, Jul 6, 2009 at 1:33 PM, weheh <[email protected]> wrote:
>
> > Hey, Massimo, what've you got against cats? ;^)
>
> ......
>
>
>
> > I just announced my first app, which has been used commercially now
> > for a few weeks and has made hundreds of paid-for reservations for the
> > club "SPiN New York". Talk about high profile, SPiN has been mentioned
> > in Conde Nast, People Magazine, Jimmy Fallon Late at Night, Good
> > Morning America, etc.
>
> I remember - I was just with a board member that week who was asking "is
> there something we can look at"; I clicked over to the site, and it was run
> in (I think it was) Ruby-on-Rails, and you explained just your piece, just
> the reservation piece...
>
> Now - I don't diminish your work, or that it is used - but I also don't have
> something I can give a board of directors and say "sure - look around this
> system, see if you like it's behavior" --- they might wind up looking for a
> RoR consultant!
>
> I looked at events:  that doesn't look like web2py;
> (it does show a version number that is only displayed in "show source"
> intentionally - it would be nice to have such a marker in webpy basic
> layout)
> I looked at membership.... doesn't look web2py either;
>
> Go look at their website. Susan Sarandon is one
>
> > of the backers. Not that she's very web saavy, but you can bet she's
> > conscious of keeping her image clean. Which means, she doesn't want
> > her website to crash.
>
> I looked around, but could not find anything that I could point a board to
> look around on their own to get to know web2py.
>
> I couldn't use this.
>
>
>
> > My web2py app was a ground-up implementation of a calendar-based
> > reservations system which is every bit as sophisticated as Google
> > calendar, with a GUI interface and a comprehensive api. It supports
> > all the "gnarly" functionality that Google claims as a reason why you
> > should use Google Cal and not build one yourself. (As a matter of
> > fact, it was a little gnarly, especially with the repeat events, but
> > web2py made it a lot easier to build IMO).
>
> Sounds perhaps like material for an article to a Python mag somewhere...
>
>
>
> > Listen. I'm not asking for Google to tell everyone to use web2py. I'm
> > just asking for Google to acknowledge web2py in the same breath as
> > Django on their "what is GAE" page. They don't have to endorse it.
> > Just say it works with GAE. For that matter, they should also mention
> > other frameworks that work with GAE. As I said before, I think if the
> > concensus here is that web2py works with GAE as well as Django does,
> > then pull the trigger and let's start a petition to get some
> > visibility and mention on the GAE page. I, for one, am 100% behind
> > building commercial-grade, heavy-lifting, production websites in
> > web2py. I may not be the world's most sophisticated web developer, but
> > it sure does the trick for me. As such, I want to see it thrive so
> > that my approach will survive.
>
> Good motivation.
>
> What I said is "I don't think they will - they use code-review publicly and
> internally, gae+django;  heck, the Android project took reitveld (the
> code-review project) and rewrote it in java for Android development use.
> They don't see anything near that scale, and won't feel comfortable _saying_
> that 'you can use web2py with our google stuff' because they want to see
> what they would be associating with first.
>
> Who can blame them?   Any small board of directors I've talked to wants the
> same!
>
> PyCon said "ok" to web2py for strength of Massimo's enthusiasm, and support
> of 2-3 people who were behind it. It was a fight, but the final
> determinant:  it was late, and they had no other viable choices before
> them.  It worked out, so they were happy in the end.
>
> Every board I've talked to is as risk averse.
>
> > And to do such a petition takes almost no effort at all in the
> > internet era.
>
> As Massimo suggested: Mention you are working w/ web2py;  stop trying to
> "control" if Google likes you or will talk about you; worry instead about
> what you can do (you can control that).
>
> If you are not willing to  see the realities I uncover before you,  then you
> will net see them and you will not be able to address them.
>
> Start building a portfolio you (we) can show others.  (and as Massimo so
> correctly points out, that is not "fluff" popularity, etc.... although if
> you build somthing that takes on as much as twitter or facebook, that
> probably won't hurt - popularity that brings a large user base is, at least,
> data!).
>
> - Yarko
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to