On Oct 14, 7:05 am, Jonathan <[email protected]> wrote:
>
> I looked through a couple of pages of the requests, and there are a
> lot of issues that I care about (and starred). There are issues there
> that are "New" from more than a year ago. How can it be that Google is
> taking no notice of this communication channel?
>
I read an interestign article a few weeks ago about the culture at
Google...
http://www.cringely.com/2009/09/the-peoples-republic-of-google/
An interesting quote from the article...
>>
At Google I am told developers bid for what they want to do with their
time. If there’s a big job to be done people commit to parts of it.
And the parts nobody commits to do? They don’t get done. Really. So
when we wonder exactly how a JotSpot, which I really liked, turns into
a Google Sites, which I really don’t like, that morphology apparently
comes from people changing what they want to change.
<<
I have no idea how true it is but it jives with what I see going on
with the Google App Engine.
Developers are adding new fun stuff like Task Queues and ignoring not-
so-fun-stuff like fixing asynchronous URL fetch...
http://code.google.com/p/googleappengine/issues/detail?id=1899
Anyway, I'm convinced that expecting Google to support the Google App
Engine like it was a real business is not reasonable cause Google is
just not into that.
I'm keeping my eye on the Google App Engine but I'm developing for
AWS.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
