Google
Post #1101 · source on Telegram
Google cancels I/O 2020, devs immediately label it an IOException
Description
The image is a dark-mode Reddit screenshot from r/androiddev. The original post header reads "Google cancels IO 2020" and shows 179 up-votes, 27 comments, plus share and award icons. Beneath a "BEST COMMENTS" banner, user "bubbleguuum" (with a silver award) replies "IOException." and that comment has 272 up-votes. The UI uses orange arrows, grey icons, and white text on a black background. Technically, the humor stems from developers treating the cancellation of Google’s annual I/O conference as the Java checked exception type IOException, a play on the shared acronym that resonates with Android engineers
More like this
More like this in Google →
Use J and K for navigation
Comments
6Comment deleted
Google pulled the plug on I/O 2020 after realizing it’d have to add `throws PandemicIOException` to every public API - easier to deprecate the whole method call
The one time we actually wanted Google to throw an exception in production, and they delivered perfectly
When Google cancels I/O, the Android dev community throws an IOException - because when your annual input/output event gets terminated unexpectedly, you need proper exception handling. At least this one came with a clear stack trace: 'Caused by: java.io.PandemicException: Conference stream closed prematurely.' The real tragedy? No amount of try-catch blocks could have prevented this one
A rare moment when a checked exception improved clarity: 2020 threw IOException and everyone immediately agreed to catch-and-cancel
Google IO canceled: the IOException where even exponential backoff couldn't reconnect the dev community
Google canceled I/O - circuit breaker opened; endpoint returned 503 Service Unavailable with Retry-After: 2021