I won't argue that there aren't still significant bugs in appengine - I had two of those issues starred already myself. But I wouldn't call them showstoppers. Even the outgoing email service, which I consider just barely functional (see http://code.google.com/p/googleappengine/issues/detail?id=965) isn't really a showstopper - it's fairly easy to use a third-party email system or even proxy mail yourself. If you have bet your company on being able to send emails, appengine isn't going to break you - it just isn't going to help you as much as you might have hoped.
I'll also point out that using EC2 doesn't make any difference in this regard. You can use Amazon SES just as easily from appengine and you can from EC2. Jeff On Thu, Apr 14, 2011 at 2:58 PM, saidimu apale <said...@gmail.com> wrote: > [a repost of my private reply to Jeff Schnitzer's just-reposted private > response] > > ---------- Forwarded message ---------- > From: saidimu apale <said...@gmail.com> > Date: Thu, Apr 14, 2011 at 5:46 PM > Subject: Re: [google-appengine] Re: Startup Weekend and Google App Engine > To: Jeff Schnitzer <j...@infohazard.org> > > > Not sure if you meant that as a private reply, I'll assume so and reply > privately as well. > >> I think this is begging the question. You only feel that GAE has >> innumerable gotchas because you are unfamiliar with it. I've been >> working with appengine (both java and python) intensively for about >> 1.5 years now and it *very* rarely surprises me. > > It is a truism that the more familiar you are with a system the less it will > trip you up; GAE is no exception. The issue is the depth of familiarity > required to avoid most gotchas, and the nature of those gotchas to begin > with. > Some gotchas are just unacceptable, whatever the experience level. Some > other gotchas are present regardless of your experience levels: > - the python app deployment tool *not* supporting two-factor > authentication: http://code.google.com/p/googleappengine/issues/detail?id=4777 > - the HR datastore appending an "s~" to the appid, breaking a lot of > commandline tools: > http://code.google.com/p/googleappengine/issues/detail?id=4671 and http://code.google.com/p/googleappengine/issues/detail?id=4374 > - a very serious issue with Google's edge caches not implementing headers > correctly: http://code.google.com/p/googleappengine/issues/detail?id=4277 > - lack of DKIM anti-spam implementation on outgoing > emails: http://code.google.com/p/googleappengine/issues/detail?id=3161 > > Not all issues are gotchas, but a disconcerting number of issues simply > should *not* be there, regardless of one's experience level. If Google > offers email services and url-shortening services, is it unreasonable to > expect that they would internally implement known anti-spam measures? At the > very least, they should prominently mention the lack of such measures in the > docs on email. > FWIW, I have intensively used GAE for about the same time as you have, so it > isn't an experience issue. Ease-of-use and rapid development, at least > compared to EC2, was a major attraction to GAE, hence my disappointment. > saidimu > > -- > 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. > -- 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.
