teh stream

teh stream

Moving back to tumblr

There are many things I want to say, but usually those things are in response to current events and internet hoopla. Tumblr seems much better suited for the commentary-style "blogging" I'm interested in.

You can find and follow me on tumblr here.

Pixelmator Playtime

I purchased Pixelmator back in 2011 during one of their early promotional sales. It's taken me this long to actually sit down and see what it has to offer. (Note that I've been using Photoshop for over 15 years, so it has been extremely easy to just glance at the Pixelmator icon and think "I'll try you next time.") Well, now that I've tried it, I have made the decision to keep using it whenever I can. The feature set is outstanding for a $30 piece of software. It's also very user-friendly from a Photoshop user's perspective—almost every function and keyboard shortcut I tried worked the same as it does in Photoshop. Hell, it even lets you open up layered PSD files! As far as I'm concerned, if you have a Mac and want an image editor, this is the app you need to look at first.

Here is the result of my first trial run. I just took an old black-n-white drawing I did back in college and started fooling around.

A Truly Inspiring Independence Day

I've been seeing myself slowly become more and more annoyed with American politics. Congress is in full gridlock—we can't even get common-sense legislation to the floor to be voted on. Our legislative government is essentially worthless. Well, a couple months ago I randomly came across a movement called "Mayday PAC". I read the plan, dug into the story behind the movement, and after listening to Lawrence Lessig's book The USA is Lesterland, decided I would join the cause. It's the first political contribution I've ever made.

Long story short, it looked like there was no way in hell we were going to make our final goal of $5 million by today's deadline. We hadn't even reached $4 million by this morning.

Well…

…and I haven't felt this optimistic about America in years.

Happy Independence Day.

New ††† album is finally available!

A mix of old and new songs from one of Chino Moreno's brilliant side projects. The album is softer and more ethereal than anything in the Deftones realm, although songs like This is a Trick and Bi†ches Brew still get my head going.

New iMac

I've got my new iMac just about set up. I went for the higher end 21.5" model with the 256GB SSD. It's replacing a seven-year-old 2006 original white 24" iMac that is actually still functioning just fine. I just couldn't take being two full OS releases behind and watching more and more software become incompatible. Apple's iApps were the straw that broke the camel's back. (I do want to give props to Apple for keeping their machines viable for so long, though.)

The screen is smaller, but due to the higher pixel density I'm really only losing 180 pixels vertically. I don't mind because I figure the native 1080p resolution of the screen will work better for Airplay anyway. (Not that I had Airplay on my 24" iMac ...yet another thing it was too old to handle.) I can't wait to test the new one out with my AppleTV.

I went ahead and decided to ignore Apple's Migration Assistant this time. You have no idea how nice that piece of software is until you start transferring things the old-fashioned way—ugh. The main reason I decided to start fresh was because I wanted to use multiple accounts this time instead of just one. With all of the social customization in Mavericks, it's really feels necessary. The kiddos are getting into computers and would love their own accounts, and my wife has always been a digital hoarder. It'll be nice being able to hang out in a nice clean/zen space going forward! Clutter out of sight, clutter out of mind!

Favorite thing so far... the SSD. Holy hell did Apple really pump up the speed with these latest Macs. When I was looking for my first SSD I remember the speed of the high-end drives being around 250MB/s ....now the high-end SATA III drives are around 500-550MB/s. I was hoping Apple's implementation was going to end up in that range too. Needless to say, when I saw write speeds over 650MB/s and read speeds over 700MB/s pop up, I did a double-take. Hot damn!



Least favorite thing so far... my dumbass decision to go for the wireless keyboard. This nubby little bastard is killing me. The eff'd up fn key location is really cramping my control+[x] shortcuts and I never realized how much I use the other delete and arrow keys. (Yeah, I know about fn+delete. It's just lame.) I'm also upset about the loss of the two easy-access USB ports. The only nice thing will be the fact that I won't be getting my daily dose of electro-shock therapy. Apple's wired keyboards eat static electricity like nobody's business. I imagine that's a healthy meal for a USB port.

All in all, I'm happy as can be. *knocking on wood* It feels great being back in tomorrow-land. I just hope this iMac will be as hassle-free as the last.

Thanks for the great Xmas gift honey. ;)

Well, it's 2014

I just noticed I didn't post a damn thing in 2013. We'll just consider that penance for my dead-wrong prediction about the iPhone 5 screen in 2012. Anywho, I hope 2014 brings me a little more inspiration and a few more people to argue with. Happy new year either way!

HBO NO!

Dove head-first into yet another discussion about HBO yesterday. You know, the one where everyone wants to pay for HBO without having to first subscribe to cable. Don't get me wrong, even though I want this to happen I do realize HBO probably won't be offered sans cable any time soon. The umbilical cord must be cut first, and ma cable is doing her best to hide the scissors.

Harry Marks was also in on this discussion, and it prompted him to write a short post on the subject. While I agree with most of his conclusions, I want to share a few thoughts of my own. The first has to do with price. Harry writes...

"The cable companies work with HBO to secure worthwhile deals for their subscribers so these premium channels don’t cost upwards of $20 per month - the starting price, Carmody states, that HBO would have to charge if one were to access the channel independently of the current cable structure."

True, HBO would need to charge more for cable-free access. $20 a month for HBO does sound like a lot, but I would certainly be willing to pay it—maybe even $25. Why? Look at it from a cord-cutter's perspective... Right now our only option is to sign up for a ~$40/month basic cable package, add HBO for ~$15, then pay at least $5 more to rent the required HD-DVR. That's $25 vs. $60+ a month—still sound expensive? "But you get 70+ extra channels too!" Sorry, not interested. I can subscribe to Netflix and Hulu+ and still pocket almost $20 a month.

If HBO needs $25 a month for a standalone subscription, then OFFER IT AT $25. Let consumers decide if that's too expensive! Unfortunately this isn't likely to happen. HBO is one of the few remaining trump cards the cable companies have left to play (live sports is another). About the only thing I see changing this is the collapse and/or reboot of the cable industry as we know it. Which brings me to...

"So, not only have we screwed the cable companies out of money (which will be reflected in a higher bill due to their needing to recoup costs), but fewer people will pay for HBO as a result of the higher prices. Fewer subscribers means less money to produce shows like Game of Thrones, which means less content and eventually no reason to pay for HBO at all."

This IS coming, and it will be painful. Painful for the cable companies fighting to stay out of the red, and painful for consumers who will no doubt be used as temporary flotation devices. While I have no faith in the current cable business model going forward, I do believe HBO can be salvaged if the shackles are removed before it's too late. Whether or not HBO goes down with the ship will be up to Time Warner. If HBO loses too many subscribers before it's set free, it may be game over.

"As much as we hate the current system, it’s the only reason we can watch shows like Game of Thrones at all."

This is one line I definitely disagree with. The secret sauce that allows multi-million dollar shows to be made is simply a large paying audience. I do agree that it's incredibly naive to think an upstart company could create a show like Game of Thrones. Any company that doesn't already have enough money to bankroll the project themselves would have a hard time finding investors. Movie studios might be able to pull it off since they already have the resources. Instead of "Direct to DVD" we could possibly see "Direct to Streaming" content, but a much likelier source would be companies like Netflix and Hulu. Actually "likelier" is being modest. Both Netflix and Hulu are already starting to produce their own original content. No, the budgets for the shows don't currently rival those of Game of Thrones, but as subscribers grow there is no reason why they can't and won't. Netflix already has almost as many subscribers as HBO (25 million vs 29 million). Being embedded in practically every TV and TV-related device shipping today should help them continue their growth. If HBO won't give people what they want, someone else most certainly will. That's the whole reason the cable industry is in their current predicament.

High quality television will find a way into existence as long as people care to watch. We won't be doomed to expensive bundles and poor customer service forever.

Don't bet on Gatekeeper making its way into iOS

The topic of side-loaded apps has been brought up a couple times this past week. Rene Ritchie gave it a mention in his article iOS 6: Higher hanging fruit, and John Gruber talked a little bit about it with John Moltz on episode three of The Talk Show (~40 min). I'm sure it's been mentioned other places as well, and now that Gatekeeper has been announced for OS X Mountain Lion I'm sure it will be brought up even more. Unfortunately, I've got bad news for those of you who are getting your hopes up.

Gruber seems a little more open to the idea than Rene—at least that's what I took away from his conversation on The Talk Show. But both of them definitely realize there would be downsides for Apple. I think Rene summed it up quite nicely in this paragraph…

Unfortunately, I don't think Apple would do this. It wouldn't really change the type of apps that are available -- for example, the system-level hacks of jailbreak -- and it would almost certainly lead to developers cutting Apple out of the 30% share of app sales Apple takes to maintain the App Store. Apple has shown they're not fond of end runs around the App Store for subscriptions, and they'd likely be even less so for paid apps.

While I believe this is reason enough for Apple to say no, I don't believe either is a true deal breaker. Yes, Apple makes a little bit of money from their 30% cut, but they are also providing a service for that fee. They host your app, provide a way for hundreds of millions of people to find it, and make it dead simple for people to buy it. They also subsidize the hosting of all the free iOS apps with that income. If developers really wanted to take all of that responsibility on themselves, I don't think Apple would mind. I also think the Gatekeeper system being developed for Mountain Lion would be a brilliant way to enable the side-loading of apps on iOS. So why exactly do I find it so hard to believe that Apple will open up the flood gates? One word …Amazon.

If Apple were to allow apps to be loaded from other sources, nothing would prevent Amazon from creating a rival store—one that provides many of the same benefits, and is even more developer-friendly. Imagine the delight if developers had practically no fear of their apps being rejected, no week-long update waiting periods, and only had to give up 20% of their earnings to be listed in the world's largest online retailer. Unless you give your app away, I think you'd be hard-pressed to find a good reason NOT to dump the App Store, or at the very least support both. I can't imagine Apple EVER letting this happen unless some legal action forces it upon them. They will not let another company jump in and undermine their ecosystem, especially one as cut-throat and beloved as Amazon. The only sure way to keep this from happening is to remain the sole app provider, and that's exactly what I expect them to do.

Amazon already jumped in and created a store for Android apps. Imagine the motivation they would have to create a store for apps that people are actually willing to pay for.

This Bigger Better iPhone Screen

After yet another round of iPhone 4" screen rumors that I simply refuse to believe, I've decided to throw my thoughts into the wild-ass speculation machine. I am not going to predict whether or not the new iPhone will be taller than the old one, that could be the case, but it's not really relevant to my argument. The claim I take issue with is the idea that the new iPhone screen will have a new aspect ratio. 

The reason I don't buy the "It'll just be taller" argument is because it wouldn't really help with the biggest problem people face using tiny screens—making small text easier to read. Text in a website, PDF, or any other document that has content at a set width will appear no larger on a +height screen than on the current one. Kind-of defeats the purpose of giving people a larger screen. Not only that, but photos (4:3) would not display as well on a +height screen either. They would need to be letterboxed, or cropped even further. Pretty much the only thing that would benefit from a +height screen would be widescreen video in landscape mode. I can't believe Apple would be stupid enough to go that route. Hell, they had their chance to do that with the iPad (a much better video consumption device), but decided the squarer 4:3 aspect ratio made more sense overall.

I find it much more likely that Apple will just keep the phone the same width (as claimed in all the rumors), get rid of the dead space on both sides of the screen, and keep the aspect ratio 3:2. A 4" 3:2 screen would roughly measure 2.22" wide by 3.33" tall. (The current iPhone screen is 1.94" wide by 2.91" tall.) According to Apple's tech specs the iPhone 4S is 2.31" wide. This means they could keep the iPhone the exact same width as the iPhone 4S if they figured out a way to run the screen extremely close to the edge. I've illustrated this below…

The resulting screen would be approximately 0.4" taller than the one on the 4S (+1 for the rumor), and the phone would be the same width it is now (another +1 for the rumor). Not to mention it would make developers extremely happy by not requiring them to support a new screen resolution. Why would Apple unnecessarily complicate things? Makes no sense to me…

Thanks to Marshall Bock for the great iPhone template.

Spotify's New Embedable Goodness

I've been a huge fan of Spotify ever since they debuted in the U.S., and today they released a really cool way to share music legally on your own websites. Instructions on how to embed a song, album, or playlist can be found here.

As an example, I have embedded one of my current favorite songs.

Enjoy.

Re: 7-inch iPad (iPod Maxi vs iPad Mini)

The difference between 7″ and 7.85″ is everything by Odi Kosmatos describes a way in which Apple could create a 7" Retina-class "iPod maxi" tablet that would be able to run pretty much all current iPhone/iPod touch apps right out of the box via pixel-doubling. The current batch of rumors are all claiming that Apple is going to release a 7.85" "iPad mini" that will run original iPad apps at their native resolution, just squeezed into a smaller frame.

"A 7″ diagonal screen (7.08″ to be exact) just happens to be the exact size of two by two iPod touch retina displays. That’s a 4″ x 6″ display surface. An iPod touch screen has 326 PPI. The 7″ screen would also have 326 PPI just like iPhones and iPods. This would yield a resolution of 1920 x 1280. This resolution would be able to run current retina iPhone applications pixel perfect using the traditional 4:1 pixel scaling, like retina displays do with non-retina apps."

There is a lot of good logic to this article, and I think it's definitely the way to go about creating a Retina-caliber mini-tablet. I do see several potential problems with this argument, though. I don't think Apple would create a Retina-caliber device without the intention of fully utilizing those pixels. This means Apple would need to create a native 1920x1280 pixel development target. Unfortunately that would create several problems for developers and consumers. First, universal apps would need to include yet another batch of optimized graphics for the device. This will do nothing but take up extra space on every existing iOS device and cause developers extra work on top of it. Secondly, would developers even be motivated enough to create a native version of their app if the standard iPhone app runs flawlessly? I'm sure many wouldn't. Unlike the iPad, an iPhone's UI controls wouldn't appear as comically large on a 7" device. Also, for the developers that do not distribute universal binaries, would you sell this as a completely separate app? If you tried, people would likely just buy the iPhone version—especially if you aren't going to rethink the UI for a 7" screen. Finally, is there even any reason for a half-tablet to exist if it mostly runs the exact same apps as your phone?

None of these problems exist for the iPad mini. The only downsides that device has is smaller tap targets, and no retina screen. I'm not even convinced the screen resolution would be an issue. It wouldn't be a Retina screen, but it would have significantly higher PPI than the original iPad and iPad 2. If Apple released this product for $299 they could definitely get away with that.

If we find out that Apple is indeed going to be bringing a mini-tablet to market, my gut is telling me it'll be the iPad mini, not the iPod maxi.

Source

Signing Up With Readability

After seeing several tweets about running into complications signing up with Readability, I decided I wanted to see just how difficult this feat was to accomplish. At first I had some doubts as to whether or not I could even sign up with the service since I post everything to a standard blogger account. I don't even have a registered domain name. Well, I'm pleased to report that neither of these things disqualified me from signing up. So just how complicated was the registration process? These are the steps…

1. Provide your name, email, domain name, and a username/password
2. Click on an emailed verification link
3. Readability creates a verification meta tag that you copy/paste into the <head> block of the HTML of your blog/website
4. There is no step four

Apparently I completed all of these tasks correctly, because I am indeed showing up as being registered. I personally do not expect to make any money from this little exercise as I have no real audience. I just wanted to see how difficult the registration process was. What's my conclusion?

Writing this post was harder than signing up with Readability.

If you have any traffic on your site at all, do yourself (and Readability subscribers) a favor by registering.

 

How Readability Could Nullify The Naysay

Some people (notably John Gruber) believe Readability is overstepping their bounds by collecting money on a publisher's behalf. I disagree, but I can see the story from the other side as well (in the right context). However, I do believe Readability could do one simple thing to quell the critics—give publishers one more option.

Right now, publishers have three options...

1. Do Nothing — This is obviously the simplest option, but if you don't want money collected in your name going to support Readability it's not an option for you.
2. Opt Out — Fairly painless, and it will keep money from being collected in your name, but it will also stop readers from being able to view your content in their preferred format.
3. Sign Up For Payments — This option will take a little extra effort on the publisher's part, and may not be worth the effort if your site isn't all that popular. It will, however, keep the money from going to Readability and will continue to allow readers to view your content in their preferred format.

What if Readability gave publishers a fourth option? The ability to donate the money collected in their name to the charity of their choice.

• Publishers that have a beef with the service would then be sending the money collected in their name towards a cause they support.
• It would be much faster/simpler than signing up for payment, and publishers shouldn't complain about being hassled because the time they spend setting things up will reflect positively on them.
• It would encourage small publishers to get involved.
• Readers wouldn't be punished because the publisher has a beef with Readability.
• It would look extremely good to potential subscribers.

I couldn't imagine this simple suggestion being anything but a win-win solution to a pesky PR problem. Am I being naive?

Subtle Stripes

Preview

Had to create a new background image for the Retina display on my new iPad. Felt like stripes this time. Feel free to download if you like.

Download Full Size Here (2048x2048 pixels)

Readability vs Instapaper

First, I want to say that I have been an Instapaper user for several years. I think the service is wonderful, and I think Marco is a cool guy. If Readability hadn't come out with a native iOS app, I'd definitely still be using Instapaper today. The fact is, I didn't switch to Readability because I like the app better. I think both apps are great! This post isn't about which app you should use, it's a response to the negativity surrounding Readability's subscription service.

As soon as Readability hit the App Store there was a flurry of articles and blog posts condemning the service. Why? Well, supposedly people are upset with the way Readability collects money on behalf of publishers. This is the dumbest thing I've read in a long time. First off, it's an opt-in service. If you don't want money from them, you won't get money from them. Second, what exactly is the downside of offering publishers a little bit of money versus nothing? It's the equivalent of a tip jar, and in my opinion it's brilliant. It's the sole reason I switched to Readability and became a subscriber. I feel better knowing that I'm helping replace any ad revenue lost due to my scraping of a site's content.

Now, lets get to the real reason behind the negativity. It's not about Readability sending money to publishers. It's about Readability swooping in and kicking Instapaper in the nuts, and Marco's friends stepping in to help a brother out …nothing more. The problem I have with all these people isn't that they are backing Marco/Instapaper, it's the fact that they are trying to make it seem like subscribing to Readability is pointless and/or doesn't benefit anyone but the people behind Readability. Bullshit. I don't remember reading one negative story about Readability when their service required you to subscribe. It only became controversial when Readability plopped their fully-functional free iOS app into the mix and undercut Instapaper.

If you are going to hate on Readability, there is plenty real motive to go around. Tell people you are backing Marco. Tell them about all the nastiness that's gone on behind the scenes of these two competing products. Tell them you hate red god damn chairs. I don't care, just don't try and tell people Readability's collecting of money on a publishers behalf is shady or nefarious unless you can show us proof. And no, Readability taking $1.50 out of $5 to support their service doesn't count. That's called a business model.

UPDATE:

After a short chat with @BenjaminBrooks on twitter I can see how Readability may upset some publishers. Readability earmarks money for publishers whether or not they have signed up to receive payments. This money will sit in a little jar with that publishers name on it for a year. If that publisher chooses not to register with Readability their jar of money goes somewhere else instead. (Back to supporting the Readability service, to a charity, or straight to a bookie …it's apparently a mystery.) Regardless, it's not benefiting the publisher even though the reader probably assumes it is. If I were a publisher that, for whatever reason, dislikes the Readability service (hates content scraping in general, thinks Readability takes too big of a cut, or just loves Instapaper) I would have to take action to make sure that my money jar wasn't used elsewhere. This means a) Begrudgingly registering with the service while trying not to vomit, or b) Contacting Readability and asking for your domain to be added to their black list. Either way, it's forcing me to act and that makes nasty feelings emerge.

As a reader, I see things differently. I subscribe as a peace offering to the sites whose content I scrape. If those particular publishers don't wish to accept my offering, I have no problem with it going back to improving Readability or being put towards a charity. Although, If I find out they are making illegal bets with it... >:(

Regardless, my original opinion still remains largely unchanged. I haven't read a negative story from anyone outside the Mac/5by5 blogosphere.

Thank you, Steve.

I didn't plan on writing a blog post about Steve's passing, but after a couple days I feel like I'll regret it if I don't. So here it is…

I only ever made it to one Macworld …the 2007 launch of the iPhone. I had no idea how significant that keynote would become at the time. I just figured I'd become one of a relatively small percentage of people carrying a great phone. I definitely didn't expect the overnight revolution of the mobile industry. But that's what took place, and I witnessed it first-hand.

That's the closest I ever came to meeting the man who shaped the majority of the tech/professional part of my life. 

I revere the experience.

Re: AT&T vs. Free-Tethering

So, AT&T is getting ready to kill users unlimited data plans if they are caught tethering. What I want to know is if they are also targeting users NOT on the unlimited plan? My guess is no, and I haven't seen mention of it in any of the forum threads I've read thus far. What you DO see is a bunch people arguing the same thing over and over, "Data is data, no matter how it is consumed. AT&T charging an extra $20 to spread the data around is robbery." While I don't find the need to tether myself, I am sympathetic to that argument with one exception …the $30 unlimited data plan. I'm not saying there shouldn't be an unlimited data plan, or that it should cost $100 a month. I'm just saying I can look at the situation through AT&T's eyes and the move doesn't make me upset. The phrase "Unlimited Data" was a great marketing gimmick back when data usage was scarce, and I think $30 was quite a bit to charge for it a couple years ago—people simply couldn't go through that much data. Now that everyone is video chatting and streaming movies and audio, things have changed and with all the network problems I can see why AT&T killed the unlimited plan. I think that's their call, and if they want to enforce the no tethering rule on that plan I think they have the right to.

Now, back to the other plans… can anyone confirm that AT&T is planning to enforce the no tethering rule on anything other than the unlimited plans? I am betting no, which means you could simply drop down to the $25 2GB data plan and free-tether to your heart's content without AT&T giving a damn. Why? Because the system can no longer be abused by heavy data users, and that's all they really want.

• 2GB = $25
• 3GB = $35 (the $25 plan + a $10 1GB overage charge)
• 4GB = $45 ("Legal" tethering plan, or the $25 plan + two $10 1GB overage charges)
• 5GB = $55 …and $10 more for each additional GB

That doesn't sound too terrible to me. If you are a free-tethering and using more than $30-worth (2.5GB) of data at their new rates I think AT&T is well within their right to force you off the unlimited plan. Go throw your hissy fit and move to Verizon (not that their plans are any better). If you are free-tethering on the 2GB plan and they've warned you that they're going to bump you up to the $45 plan if you don't stop …that's when I'd call shenanigans.

Original iMac HD vs. OWC FW800 SSD

My first generation white 24" iMac has been running extremely slow lately. I'm not sure if the internal HD is on it's last leg or if I'm just getting accustomed to the SSD speeds at work. In either case I'm trying to get another year or two out of my iMac before I upgrade and I figured the only way to do that was with an SSD. Unfortunately replacing the internal HD in this particular iMac is a pain in the ass. I'd pay someone to do it for me if it wasn't already out of warranty and I had some sort of guarantee it wouldn't crap out on me in a month …but that's not the case. So I decided to test an external FireWire 800 SSD solution instead (115GB OWC Mercury Elite-AL Pro Mini). I know that a FW800 connection is nowhere near as fast as the peak throughput of an SSD, but the main benefit you get with an SSD is crazy fast random access speeds. I figured that would help significantly speed things up even over a FW800 cable. The video below shows the results. The FW800 SSD is on the left, my old HD is on the right. YouTube screwed up the speed of the video upon upload, but I thought it being sped up might help keep your attention. The stopwatch is running on my iPad under the screen. I shot both videos with my iPod Touch, then I played them back simultaneously and shot my iMac's screen. Crappy, I know, but I've got other things on my todo list.

In case what is happening in the video is unclear, the SSD was over 5x faster. (0:51 vs 4:48). I don't know how bad off my original HD is (it's over 4 years old and I'm sure a new HD would fare better), but I can easily say the SSD is a no brainer …even when throttled over FW800.

Here are some benchmarks from the drives themselves. Open the images in a new tab to view full size.

Original HD – QuickBench: Note that the sequential reads/writes are much higher than the SSD in this test, but they seem to be lost in the large file test below.


OWC FW800 SSD – QuickBench:


Original HD – Large File Test:


OWC FW800 SSD – Large File Test:


Original HD – Xbench


OWC FW800 SSD – Xbench

If you have an old iMac I highly recommend this upgrade. If you have any questions/comments you can ask below or hit me up on twitter @zwei.

Google, it’s a bit late to pull this crap.

So Google just announced that they are dumping h.264 HTML5 <video> support in Chrome. Apparently they want you to believe this is the just another step towards that daisy-fresh “100% open” utopia of the future. Hell, they may actually be blind enough to believe it themselves. They have decided to put their weight behind their own WebM codec with the hopes of it becoming relevant, but in reality this move will probably do very little to help. What it’s going to do instead is throw a wrench in the creation of the HTML5 <video> standard, and it’s going to throw a lifeline to Flash. The first consequence benefits no one, but the second benefits Google by keeping a key differentiating feature between iOS and Android relevant in the eyes of consumers.

Unfortunately for Google, none of this matters. It’s simply too late in the game to change course. Apple has over 100 million iOS devices in the wild, and regardless of a HTML5 <video> standard, Apple is going to support h.264 <video> (as will Microsoft), which means web developers are going to support h.264 <video>. Not to mention the fact that WebM doesn’t support hardware decoding—something critical in the mobile web space (where HTML5 <video> is most relevant). Even if WebM does gain hardware decoding, nobody but Google is going to waste their money encoding and hosting two versions of the same video. Why? Because Flash supports h.264 so users can be served the exact same h.264 content, albeit unnecessarily wrapped in a Flash container. Way to shoot yourself, and your users in the foot Google.