I can understand the frustration when there seems to be little movement on something that is important to you (Django 1.0 in your case). You'll have noticed that the app engine team (and Google generally) are very careful not to provide deadlines, which is a sign of a development process managed by developers. Deadlines are usually arbitrary dates set by sales managers who don't understand that software development is lumpy.
Google's other problem is that everyone wants something different. Many people seem to want a simple LAMP replacement, java, SSL, bare domains, billing (an end to quotas)... oh yes, and Django 1.0! Given they have limited resources, I think their solution (the star driven issue list) is a fair solution, and again smacks of a developer-driven process. So if what you want is firm deadlines (resulting in buggy compromised solutions) and development priorities set by a suit (who absolutely won't understand the difference between Django versions), I think you might want to try the cloud service from the other crowd (the one that makes buggy compromised operating systems too ;). Your point about chatter on this list is true - it also occurred to me the other day. My guess is that Google are waiting to see how Appengine is received before pumping lots of cash into promoting and developing it. If you like the model (I do *a lot*) then develop successful apps on it and publicise them - show the world that Appengine is an excellent platform. That'll give Google the confidence to invest in it's continued existence. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
