On Mon, Oct 6, 2008 at 9:20 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Jorge, > > One thing you have to remember it is not what Guido or the engineers > want. If Google App Engine is to succeed it is what the customers > want. If it is designed as you have stated it will never recoup what > Google has spent so far let alone down the road. Google App Engine has > so many many limitations. Regardless if the limitations are by design > or not it is virtually unusable by 99% of all developers. Can Google > make a business off the remaining 1%? > Leaving aside your exaggeration on the numbers. You got it wrong, to paraphrase the talk, BigTable and by extension GAE's db store, is ablel to expand to infinity storage, the only possible limitation is the number of machines it is configured to use and that can always be expanded. Which means these are not design limitations, they are resource optimization. The restrictions are in place so you are encourage to use resources efficiently. And they will be set higher in cases where needed. An example is the "top gae applications" they had their quotas raised.
Lets look at it from a performance perspective. 1- 1MB datastructure - which unit of data (leaving files outside) should be bigger than 1mb? IMO that's a badly design datastore. 2- 1000 query limit, which user is going to want 1000 results? 3- Short CPU, it is common knowledge that a user will go away from a page after 3 seconds of loading. so in order to eliminate this bottleneck you use catching, after all if it's intensive to compute it's worth catching. 4- Quotas in general, not even google has enough machines for us to waste. 5- Admin, a django junkie complaining for the lack of UI The only concern where I agree is file upload, we do need a facility to uplod videos or pdf or images or whatever we want, but that is being worked out, same with SSL. Funny that the OP didn't mention SSL as that IS a showstopper for a LOT of applications http://code.google.com/p/googleappengine/issues/detail?id=15 > I think Google should pay much more attention to what the posters here > are asking for and less on what they have "designed" App Engine for. > Failure to listen to your customers is Always a Mistake! Defend it if > you like. App Engine is going to be a huge money pit for Google. > Engineers are terrible Businessmen and even worse Marketers Guido said > as much in his talk. > > In the end Google is a publicly owned corporation and not a University > and ultimately Google must answer to its customers and stockholders. > The goal is to increase shareholder value through offering products > and services the broad market demands and not basic research. App > Engine in it's current form seems more like someone's thesis project > more than a marketable computing platform. > > On Oct 6, 5:13 am, "Jorge Vargas" <[EMAIL PROTECTED]> wrote: >> On Sun, Oct 5, 2008 at 4:47 AM, Aral Balkan <[EMAIL PROTECTED]> wrote: >> >> > Hi Jorge, >> >> >> You clearly don't get must of the stuff you are talking about. >> >> >> ALL the quotas are there for you to be efficient they the whole >> >> purpose, they are not hard coded to make your live bad they are in >> >> there to make the system better. >> >> > I feel that you have missed the point of my post. Rest assured that I >> > get the stuff I'm talking about. >> >> > Please re-read the post and you will see that it is not an attempt to >> > bash Google App Engine. Quite the contrary, it is a simple summary of >> > the issues encountered by one developer while developing a real-world >> > application. The reason for the post is to highlight these issues so >> > that they can be fixed and thus, ultimately, to improve Google App >> > Engine. >> >> > As you can see from the replies here, and on the post, I am not the >> > only one who has encountered these issues either. >> >> > We provide constructive criticism for the things that we care about so >> > that they can evolve. I invite you to add value to the conversation >> > and help make Google App Engine better. >> >> did you watch the video I posted? they are aware of anything you >> propose, and half of them are non-fixable specially because they are >> impositions made so the system won't crumble with bad code, the other >> half are being worked on and as Guido suggested will probably be out >> before the end of the year. >> >> > Aral > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
