Winer’s explanation is purely speculative, and some might call it a conspiracy theory. But it points to a big issue for free speech in the cloud: what happens if one, smaller customer criticizes a bigger customer? In the Web 1.0 era, if you got kicked off a Web host you just found another. Today, the number of providers like AWS are small. As AWS’s promotion material points out, cloud computing gives smaller outfits the ability to take advantage of high-performance computing.

So are Amazon and Apple jeopardizing small(er)-fry companies to keep their lucrative Federal contracts? What does such action mean for customers of all sizes? That’s what Klint Finley asks in Read/Write Web’s Amazon Web Services, WikiLeaks and the Elephant in the Room.

So Apple announced the iPad, and it won’t support Flash.

That shouldn’t be a surprise. Neither the iPhone nor iPod Touch support Flash. Indeed most mobile platforms don’t (yet) support Flash. Even the smartest of smart phones have limited processing power and storage space compared to laptops and desktops.

According to Steve Jobs, Apple doesn’t support Flash on its mobile devices because “it’s buggy.” But I’d guess their decision has as much to do with Flash’s capabilities. Many of the products in that cash cow known as the Apple App Store could be developed using Flash instead.¹ Supporting Flash would undermine that billion-dollar revenue stream, piss off iPhone / iPad developers, and also put Apple at Adobe’s mercy.

Besides, everyone’s moving towards HTML5, right? Well yes they are, but not so quickly. I wouldn’t rule Flash out for another 3 to 5 years.

Why do I say this? Four reasons:

1. Flash has inertia on its side. Major content sites such as Disney and Hulu still use Flash to deliver video, animation, and interactive experiences. According to Adobe’s statistics, Flash has over 90% penetration in mature markets. Developers already know how to use Flash and ActionScript to create these experiences. In short: there are a lot of folks invested in Flash as a platform.

2. HTML 5 isn’t quite ready for prime time. It’s a shifting standard, a work-in-progress. Though even Internet Explorer 8 supports some significant HTML5 features, Internet Explorers 6 and 7 do not. And both browser versions are still used widely enough that dropping support is not an option for most developers.²

3. Flash is still the best cross-browser, cross-platform way to serve audio and video. Safari / WebKit, Firefox / Mozilla and Opera all support the HTML5 video element. They do not, however support the same codec.

   Apple is squarely in the H.264 camp. Google paid a licensing fee so that it could include an H.264 decoder in Chrome. H.264 is a patented codec. Any browser that wants to enable H.264 video will need to pay a licensing fee.

   Licensing fees and patent concerns are why Opera and Mozilla are backing Ogg Theora. Ogg Theora is an open sourced codec with no known patents. I should add here that Chrome also supports Ogg Theora. Google, perhaps wisely, chose to include both.

   The big monkey wrench in video element adoption, however, is Internet Explorer. Internet Explorer is waiting for them other fools to work out that default codec business before it implements support for the element.

   And all of this is before we get into the differences in how browser vendors will execute the specification. That’s a whole ‘nother headache.

   We will be using Flash until clients are willing to pay for separate Safari, Firefox and Internet Explorer video integration or until the HTML5 working group agrees on a default codec.

4. Adobe is working to bring Flash to other mobile platforms. As Adobe’s Chief Technology Officer Kevin Lynch explained, We are now on the verge of delivering Flash Player 10.1 for smartphones with all but one of the top manufacturers. This includes Google’s Android, RIM’s Blackberry, Nokia, Palm Pre and many others across form factors including not only smartphones but also tablets, netbooks, and internet-connected TVs. Could the iPhone and iPad’s lack of Flash support be a deciding factor in consumers’ decisions not to buy an Apple device?

My Prediction for Flash

I suspect that as HTML5 gains prominence, Flash will — eff that, it should — shift from an authoring environment for its proprietary SWF format to one that generates HTML, CSS, JS and SVG code for the browser. I think the building blocks for such software are in place. Flash Builder (formerly Flex Builder) for example, eliminates (most of) the need for FLA files. Perhaps developers will one day use a mix of ActionScript and JavaScript in the Flash Builder authoring environment to create web-ready assets and animation that don’t require a browser plug-in.

Mobile-friendly Web Development Right Now

Despite the fact that Flash is supposed to come to every other mobile platform, Apple’s decision to keep Flash off of the iPhone, iPad, and iPod Touch is not without impact. Apple still runs the smart phone market; in some ways they drive the mobile web. That means the prudent path is (still) progressive enhancement, and ensuring that your critical content and navigation are built using HTML.

So will I buy an iPad?

Nope. I have a laptop, a smart phone (a T-Mobile G1), a desktop and an iPod Touch. To me, the iPad is that weird spot between my smart phone or iPod Touch and a laptop with the convenience of neither. It doesn’t have the pocket-sized portability of my iPod Touch or my phone. And it doesn’t (yet) have the robust features of a laptop — USB ports, optical media drives, and the ability to install any app. I can’t justify the value for the price.

Besides, I still much prefer books to e-readers. I can sell books, trade books, leave books, loan books, and get books wet. I am not about to soak in the tub with a $300 device, but I would with an $11 book.

What do you think about the iPad, Apple’s decision, or the future of Flash and HTML5?

¹ Many of these apps could also be built using HTML, CSS and JavaScript, but there’s no money in that either.

² There are scripts available to make IE act right, of course. ExCanvas, for example, mimics support for the canvas element in IE. Simple HTML5 isn’t much different from HTML 4.01. You can actually forge ahead with HTML5 now if you don’t need advanced features like DOM Storage.

In order to release an iPhone application without having to submit it to Apple’s insane App Store process, developers could just use Web technologies and create Web apps instead of native apps.

In other words, iPhone developers are doing it wrong. By focusing on native applications, they are subjecting themselves to Apple’s approval process unnecessarily. Safari, he argues, is all most application developers need, and the reluctance of iPhone developers to embrace web technologies has more to do with snobbery than functionality.

The fundamental problem on the iPhone is not Apple’s App Store approval policies, but the iPhone developers’ arrogant disdain for Web technologies. … They dismiss Web technologies as toys for children. JavaScript is just this little language that cannot possibly compare to real technologies such as the one they’re using. HTML is too simple. Real programmers don’t do that stuff. As to Web developers, they are just glorified pixel-pushers that should in no circumstance be taken seriously.

I agree that most iPhone applications don’t need to be native ones. I also agree that many developers — not just iPhone developers — dismiss client-side programming as kid stuff.

I suspect, however, that iPhone developers really prefer native applications because they’re trying to make money. Apple’s App Store lets developers get paid and helps them protect their product with a degree of digital rights management the web doesn’t provide.

So I bought it, but I bought it, for the first time, with misgivings. I felt the way I’d feel buying something made in a country with a bad human rights record. That was new. In the past when I bought things from Apple it was an unalloyed pleasure. Oh boy! They make such great stuff. This time it felt like a Faustian bargain. They make such great stuff, but they’re such assholes. Do I really want to support this company?

Graham continues with why Apple should care. The short version: don’t piss off the kick-ass developers you might want to have work for you one day.

But the hoodie belonged to the Noughties. I don’t believe it was just about the ASBO generation hiding their faces from CCTV, either. It’s more practical than that. If you spend all your time hanging around on the street in a coldish, wettish country, a hood will keep you warm, and stops the rain spoiling your hairstyle. Plus it creates a safe anonymity for a teenage boy to hide in: if you’re a skinny, pimply 14-year-old who has to deal with a lot of confrontation, putting your hood up means that, from behind at least, someone might take you for something more dangerous than you really are.

From The Economist’s More Intelligent Life blog.

Also mentioned: Apple everything, poor-quality pixellated images, Eindhoven design academy, anti-modernism, Frieze magazine and Bernie Madoff’s smile. Also see, More Intelligent Life‘s The i-Decade.

Something I learned while digging around the System Preferences on my MacBook: Mac OS X features what they call “Trackpad gestures.”

Depending on which Trackpad gestures you enable, you can:

• Scroll by dragging two fingers down or across the trackpad.
• Enable the secondary click menu (the equivalent of Ctrl+click, or the Mac’s version of a right click) with two fingers on a trackpad plus a trackpad button click.
• Click by tapping the track pad (rather than the track pad button)

To enable, go to Keyboard & Mouse under System Preferences. Trackpad gestures are at the bottom of the dialog box.

It takes a little while to retrain your brain to use the gestures. But I like that I don’t have to reach for the Ctrl key when I want to bring up a secondary menu. To me, anything that decreases the amount of finger dancing I do with my keyboard is a good thing.

I do find, though, that the click-pad tap can be a little too senstive. Either that or I need to adopt a feather-light stroke.

I also like the two-finger scroll. Much easier to manage, in my opinion, than the two-handed scroll option (one hand holding the trackpad button while the other hand scrolls), or the one-handed scroll motion of death (using your thumb to hold down the trackpad button while using another finger on the same hand to scroll). Now I have no reason to go anywhere near the scroll bar.