Posted February 21st, 2012 @ 06:08pm by Erik J. Barzeski
Jesper has some good points about the loose ends Apple has yet to answer.
Daniel Jalkut asks Apple to Fix the Sandbox, which isn't really Mountain Lion specific, but is still looming ((Even with the pushed-back - again - deadline, it's looming.)). I'm not keen on his suggestions, but they started a discussion so they're valuable for that alone.
FWIW I don't pirate things. I sell software, so I think it'd be incredibly hypocritical to steal things while expecting others to pay me for awesome software.
That said, I no longer watch DVDs anymore, either, and were I to begin pirating, I'd probably start with DVDs. Disney - though they seem to love the "unskippable" sections - at least gives you the Blu-Ray, DVD, and the digital version of the movie when you buy it.
P.S. Most of the movies we watch we do so at the dollar movie theater, which costs as much as $2 during peak days and times.
P.P.S. Image originally from this article by Matt Gemmell.
Posted February 17th, 2012 @ 11:28am by Erik J. Barzeski
News is just now coming out about Gatekeeper in Mountain Lion (OS X 10.8). It sounds like a reasonable compromise, but my concern is that this is a stepping stone towards Apple locking down Mac development even further. A quote about sacrificing liberties for a little protection and deserving neither springs to mind.
Still, I'm not opposed to the idea of Developer IDs and making that the default setting in Gatekeeper, particularly if I can choose that setting and still launch and run code that isn't signed simply by confirming that I'd like to do so.
But I will say that Apple needs to:
Ensure that Developer IDs are relatively easy to obtain.
Are targeted at the specific group or individual, so that someone can't obtain an ID, found to be distributing malware, and then easily obtain a different ID.
NOT fool around with saying what is or isn't malware. A broad definition should be provided and rigorously adhered to, because porn or political apps or apps that "have enough competition already" are not necessarily malware. Imagine how lousy it would be for someone's competitor to allege malware and have Apple take action?
Do a better job than they've done with the iOS App Store.
NOT go beyond this stage. I will not appreciate having developers feel "squeezed" into the Mac App Store.
Those are my concerns. I hope this is a good thing, and I'm giving Apple the benefit of the doubt here. Famous last words, right?
P.S. Analyzr Pro and Analyzr Student are niche apps that cost $59 and $299-$599. We regularly offer coupons and discounts, etc. We like knowing who our customers are simply so that we can provide great support (we don't even email them). As such, we're not keen to put our apps in the Mac App Store and would resent any pressure to do so. Getting a Developer ID, however, represents no pressure to do so, again so long as it's easy, inexpensive, and fairly handled.
Posted February 14th, 2012 @ 09:40am by Erik J. Barzeski
I'm just now getting around to reading Steve Jobs by Walter Isaacson, and though I know I'll learn little new from the book, I'll still get through it.
You could learn more about Steve Jobs's work by reading Rob Walker's 2003 New York Times Magazine piece than by reading Isaacson's book, but even then we're left wanting for the stories behind any of Apple's products after the iPod. Isaacson's book may well be the defining resource for Jobs's personal life — his childhood, youth, eccentricities, cruelty, temper, and emotional outbursts. But as regards Jobs's work, Isaacson leaves the reader profoundly and tragically misinformed.
It's disappointing that the last and best opportunity to get to know Steve Jobs was squandered by Walter Isaacson. Nobody thinks Jobs always made the best decisions, but it's sad that his poor choice of Isaacson will be regarded by many as his last decision.
Posted February 12th, 2012 @ 11:17am by Erik J. Barzeski
I vaguely remember watching this. It wasn't as impressive at the time - I remember thinking more that it was odd she was wearing a track suit or something than how well she performed.
Posted February 8th, 2012 @ 09:18am by Erik J. Barzeski
If you search the Intertubes you'll find a few instances of people asking how to block someone from iMessaging them.
Through your carrier, you can block someone from calling and texting you, but Apple has yet to provide a way to prevent a number (or ostensibly an email address) from iMessaging you.
Suppose for instance someone from your past is harassing you. You can block them from calling, and you can block them from texting, but unless you disable iMessage system-wide, you cannot prevent them from iMessaging you.
Apple should add the capability to block iMessages from certain numbers/email addresses.