For what it's worth, you're a fantastic writer and this is one of the most enjoyable articles I think I've ever read. You've captured the essence of the subject perfectly, and your writing style is thoroughly enjoyable.
Seconding this. Maybe it's my love of anecdotes and analogies to illustrate points that may be hard for people to understand. Possibly it's my appreciation for well placed juvenile humor.
Either way, I identified with some of the points being made and easily picked up on the things I'd not considered from this angle thanks to the funny examples.
Everything above echoed, with the important addition that I feel I can share this article with all of my non-techy friends and family and feel they will step away with a much better understanding of the Apple discussions.
I still see unease with some of my friends and family about the topic, and although perhaps some of them have realized the ultimate question of should the cockpit or the cabin control things, I don't think they have a good understanding of why that is, or how this phone security compares to other things that are called "security," whether a door lock or the airport security line.
Very vivid writing that explains this for everyone. And I dig this type of humor.
I liked it. However, I'm not going to forward it since it will confuse people who don't have the background to disambiguate.
For example, who is "you" in the following two bullet points:
It is not 'secure' as the Coke recipe is secure.
Coca Cola has the key to its vault, but you don’t
have the key to yours.
It is not “secure” as the Pentagon is secure. Those
blueprints are closely guarded, but your plans — even
much of your security code — are known to all.
The article is about software security and how it compares (or doesn't compare) to real-world security, and what this means for the Apple case.
What drew me in is mostly that the beginning is written in a very light-hearted style, so it's a pretty easy read at first.