This is an atypical Labs post, as it doesn't really concern specific code at all. It's more of a wake up call. It starts with the same thing you've been reading about everywhere -- the iPad. It ends somewhere much different and much more important for our industry. It's a conversation about what we're doing as experts in this field and how we move forward together.
The announcement that the iPad won't support Flash kick started a lightning storm of opinions. The alleged issue at hand is that the iPad doesn't support Flash. This is a bad thing. It's a bad thing for the same reason that it also doesn't support Google Chrome, Firefox and (even) Internet Explorer. It's a bad thing because it doesn't support Unity and Java. It's a bad thing because it supports what Apple wants it to supports and that's all. Which isn't to say that we don't love making Apple applications... because we do. It's just that the iPhone app store was an incredible leap forward from the previous generation of mobile applications and so was rightfully recognized as revolutionary. The iPad isn't revolutionizing netbooks, it's devolving them back to a fully closed era. One environment, one language. A cumbersome, time consuming distribution process.While you can certainly be expressive using Objective-C and with the iPad, the decisions on how a user engages with something we make should be left to the experts.







