Well since the book piracy has been compared to movie piracy in your article, I can use that comparison here in my argument. Movies cost millions to make, yet the cost of watching the movie in a theater is 9-13$ depending on where you live. But there, the theater costs are inbuilt into the price as cost of running the theater is added to the price of the ticket. Now in a DVD, the cost of reprinting the DVD is probably 1$, so why should the DVD cost 20$ for a movie. Hence they get pirated. It's the same with books, a 41$ e-book is quite expensive. If someone is buying many books, it adds up. Those who buy lots of books do think about the total amount of money they spend on their books, yours is not the only book they are buying. So giving the argument that it took time to write a book and that's why it costs more is flawed. There are various tricks you can pull in selling e-books like selling 2 or 3 different titles together for a discounted price that makes it worthwhile to buy etc. Of course, the old business model of high price dead tree book leading to unfathomed riches for life is going to go the way of the dodo.

Actually, maybe offer the e-book for say 2$ and see how many buys you get. 50$ for a book might make people think twice before they buy, but 2$ for the book might actually generate more volume of sales for you. Those who pirate only do so either because they are not interested in buying the book at all, or they cannot afford it. But by making an authentic e-book version affordable you can increase volume sales because it becomes really cheap to buy. Replication of an e-book copy really costs no money unlike its dead tree counterpart, so instead of asking the question about how to control piracy, why don't you ask the question about why should e-books cost so much as the dead tree versions ?

there were a lot of returns because people didn't know what to do with it.

As opposed to "Windows" which they can open ?

I never use Interface Builder. It sucks. I "programmatically" do everything from adding labels, to buttons to text views to anything for that matter. It is much easier to code up than use Interface Builder. This is just my opinion though. Apple's documentation is pretty good in explaining how to code up everything.

By counting Cowboy Neal's balls in binary...

But if you can create "macros" and modifications to your right click menus, then you ought to be able to save them in some standard format to be exported to another Office version, just like you can do with bookmarks in browsers. No ?

isn't that actually a problem/limitation with the hardware ?