I learned Python specifically for working on GAE. I reasonably suck at the language but it had advantages of reduced overhead which I thought would make it the ideal choice for GAE and enterprise class deployments where 5% increase in performance meant 5% on my bottom line.
Everything I read says that GO is great for multi-threaded Applications. Awesome! Then you read the Google bits: The Go runtime environment for App Engine provides full support for goroutines, but not for parallel execution: goroutines are scheduled onto a single operating system thread. This single-thread restriction may be lifted in future versions. So.. Do I port my python app to Java knowing I get multi-thread and can save a crap ton of money on instances when the new pricing hits? Or do I port my code to GO expecting that it will be the multi-thread homerun that it is on other platforms? OR.(highly unlikely) Do I hope that GAE makes the instances smaller and cheaper when running python so that I can get $.02 per hour instances that are 1 4th the size so they run at 100% cpu instead of 25% cpu? Essentially I'm asking "It appears in the new paradigm pricing was optimized for Java, is this the case or is it optimized for GO and Java just gets the benefits right now, or is Python really what GAE was born for and will it come back to being the cost favorite?" -Brandon -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
