Nowhere in this thread is the word "risk" used. Bottom line, there's probably a reluctance to bet on web2py when it's not a known quantity in an application with the stated demands. Most people are risk adverse because they don't want to get beat about the head and shoulders if something turns out not to work. At least with .Net one can always claim that it's used successfully in large scale systems. Massimo's suggestion to quickly and cheaply build and test a prototype is the best idea. Then if it works, it works. You're dealing with facts and not theory.
On Nov 29, 12:56 pm, Lorin Rivers <[email protected]> wrote: > The project I'm working on has hired a consultant who is now recommending > .Net in place of web2py or even rails. > > What's the 'largest' scale web2py is known to perform well on? > > -- > Lorin Rivers > Mosasaur: Killer Technical Marketing <http://www.mosasaur.com> > <mailto:[email protected]>512/203.3198(m)
