John Gruber responded to this quite succinctly, which is that this isn't "embrace, extend, extinguish" because Apple isn't calling their .ibook format ePub. They just happen to use ePub + custom extensions.
This is a false dilemma. Authors don't have to use iBooks software to author ebooks and users don't have to use iBooks to read ebooks on the iPad (and they probably don't because it's really buggy). Problem solved.
Let's see how many comments we can get explaining why this was bad when Microsoft did it with IE but just fine when Apple does it with iBooks.
Bonus points if you somehow spin embrace-extend-destroy as a good thing by conflating what's good for the users with what's good for Apple and its shareholders.
I still don't understand how they are getting away with the 'agency model' for ebooks. With those deals, no one but apple can make money selling ebooks in a native app on an iphone/ipad.
Most companies are using the open standards of the web and using them to build their own closed standards. Apple isn't the only one, Amazon et al are as guilty as everyone around. Hardware lock-in from the previous decade has now moved to content lock-in on the Internet.
8 comments
[ 3.7 ms ] story [ 24.8 ms ] threadLet's see how many comments we can get explaining why this was bad when Microsoft did it with IE but just fine when Apple does it with iBooks.
Bonus points if you somehow spin embrace-extend-destroy as a good thing by conflating what's good for the users with what's good for Apple and its shareholders.
The closest to that would be Amazon, whose reader doesn't support epub at all.