On Thu, May 12, 2011 at 1:15 AM, stevep <[email protected]> wrote: > On May 11, 9:57 am, Geoffrey Spear <[email protected]> wrote: > > For Python applications, yes, a single request takes up all of the > > resources of an instance for the time it's being handled. Java > > instances with threading enabled can handle multiple requests. > > Fundamentally (although the clothes are still in the wash, not on the > line) the old cpu-based resource charge was fair. > > Unless something drastic changes, the new instance charge model > appears heavily, very heavily prejudiced against Python. > > Egregious in the extreme. Making a decision so unfavorable to one > group is weird. Likely so weird that GAE should stop with > justifications. > > Maybe it all works out, but this looks just so weird, so very weird to > me. Why punish Python developers?? > > If we read between the lines, as we must since concrete info from Google is so scarce, it appears Python's status in App Engine is very slowly being diminished. Google clearly would prefer to see Go as the main language runtime (since they created the language), hence the push to have Go be battle-tested by developers (who will then get screwed when the rug gets pulled out under them sometime in the future).
Java is also probably not completely safe, at least not given's Oracle's ownership and aggressive moves wrt Google/Android. -- 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.
