When I say "enterprise" I do not mean "large businesses", I rather
mean "businesses and non profit organizations" that use computers and
follow a more or less professional software development cycles.

I agree with you that small businesses are more profitable and a
better market for web2py than large enterprises.

Massimo

On Jun 3, 9:07 pm, JohnMc <maruadventu...@gmail.com> wrote:
> Massimo,
>
> Following Horst's observations from a different angle.
>
> 1) Don't worry about whether Web2Py is 'Enterprise Ready'. That is
> Tech Press/Vendor Spiel to create marketshare with appeal. Its verbal
> junk. Go take a look at table 2a 
> --http://www.census.gov/epcd/www/smallbus.html
> . The tally of firms <100 employees to those >100 outrank them 10x.
>
> The number of firms with budgets that support $1m+ software projects
> is less than 20k. There are probably 100 'Enterprise Providers' (eg
> Microsoft, IBM, Sun, Oracle) chasing that small field.  So when I hear
> a programmer state they do 'Enterprise level production development'
> like some badge, Django or otherwise they too are chasing that small
> field of money. Most likely as a member of one of those 'Enterprise
> Providers'.
>
> 2) The opportunity is in that <100 employee range. Those firms rarely
> have million dollar budgets. Nor do they typically have the budgets to
> buy WebSphere platforms or SAP software. But their need is just as
> great for specialized software.
>
> Better to cater to the smaller firms who would benefit from web2py. It
> is just as important to be able to be profitable in the small scale as
> the large. Fact more so.
>
> That Web2Py can scale is the icing on the cake.
>
> JohnMc
>
> On Jun 3, 7:30 pm, Horst Herb <my.list.subscripti...@gmail.com> wrote:
>
> > On Thu, Jun 4, 2009 at 10:19 AM, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > > because those people are influential people in the Django community,
> > > the same people posting negative comments about web2py everywhere.
>
> > I am not sure whether such comments matter.
> > People seriously using such development tools will have a good look
> > before they embark on an expensive journey anyway, and I think in that
> > regard web2py has a lot going for it apart from the lack of usable
> > up-to-date documentation
>
> > Let's get good apps out, that will spread more good word about the
> > tools we use than any silly comments on time wasting web sites
>
> > I for my part can vouch that so far development with web2py has been
> > - a bit faster than with RoR
> > - far more legible code than with RoR
> > - I managed to hire 4 good people so far to to web2py work for me.
> > They seem all competent, and so far have delivered in time and to
> > specs. No exemption so far, and that's a quite unique experience for
> > me (when developing a similar project with RoR I had hundreds of
> > applicants but in the end nobody delivered in tiome and to specs and
> > it turned into a financial nightmare until the whole project was
> > shelved)
>
> > This weekend I am going to present the first version of my medical web
> > app (pre alpha, but seemingly functional) at a medical conference. If
> > acceptance is good and no major hickups during demo (when lots of
> > doctors are going to hammer it all at the same time) we'll go public
> > with the project. I am then happy to give a testimony on theweb2py web
> > site of our experience so far, including the exceptional experience of
> > being able to easily hire good competent developers familiar with
> > web2py, as well as the incredible responsiveness and helpfulness of
> > this list with a very low signal:noise ratio
>
> > Horst
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to