On Sun, Jul 22, 2012 at 2:12 AM, Drake <[email protected]> wrote: > > Let's see... You spend your life complaining how the platform sucks. I > release tutorials on how to make it suck less. I'm the troll?
This conversation was constructive and mostly positive until you chimed in. It was a reasonable discussion of real problems that many people are having with scheduler behavior, including concrete suggestions for how to improve it. For the record, I have never, ever said that GAE sucks. Your advice, on the other hand... > Anyone who thinks the low level api is analogous to assembly probably > doesn't want to depend on me because the laughter when they asked a question > might be deafening. > > Read EVERY optimization guide on Java for GAE and that is the first thing > they tell you to do. You have this wrong. It's true that the JDO/JPA module gets a bad rap, but every optimization guide I've read recommends abandoning it in favor of lighter-weight layers like Objectify or Twig. It's true that these tools will give you a better startup time because they don't do classpath scanning. But it turns out that avoiding classpath scanning only gets you so far - the up-front cost of classloading and inspecting persistence classes becomes significant when you reach a critical mass of entity classes. As for writing complex business applications using strictly the low-level API... good luck. I can only explain your attitude about this as naïveté. And your absurd proposal that all 326 of my url endpoints should be separate applications... Just. Wow. Jeff -- 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.
