605 karma · joined March 24, 2007
Incidentally, I have been playing around with the concept myself (client work) and it turns out you can hack a semi-working solution in just a handful lines of js:
https://bugzilla.mozilla.org/show_bug.cgi?id=843310
Reporting to Chrome has been even worse. No word, no nothing. Not even a confirmation. (Although the submitting process itself has been simpler AFAIR).
That's really uncool, after a few of those you lose interest in submitting any more since the feedback feels like "we don't care". So you end up using the time to find workarounds instead.
Now obviously someone will point out everyone can go ahead and submit a patch for the bug itself since it's open source. That's all cool and dandy, I love open source as much as the next guy, but please, let's get serious. Who has the time to dive into a massive codebase like that and fix the bug? Not everyone has plans to become a browser developer.
500-series errors indicate that a request didn't succeed, but may be retried. Though infrequent, these errors are to be expected as part of normal interaction with the service and should be explicitly handled with an exponential backoff algorithm (ideally one that utilizes jitter).
However, I still think hosting on S3 is a great option. They are pretty reliable anyway.
$ ./sublime_text
Fatal Python error: Interpreter not initialized (version mismatch?)
Aborted
$ python --version
Python 2.6.6
Is that my python version? Could the error message be more verbose, or is it not coming from sublime?
How do I go about fixing that? Wanted to give sublime a try...