Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Jonathan Feldman

Jonathan Feldman

Contributing Editor

Apple Obsolescence Debate: More Analysis Please, Fanboys

The Apple-can-do-nothing-wrong crowd cranked up the hate machine when I questioned the vendor's upgrade treadmill. Some responses and clarifications are in order.

"MobileMe is ending soon." Those four words, combined with the revelation that for iCloud, MobileMe's successor product, Apple is dropping support for the version of MacOS on my one-year-old laptop, prompted me to write a column on June 25 questioning whether Apple's upgrade treadmill would be palatable to CIOs.

That column led to some serious debate and discussion on InformationWeek.com, but it also brought out the mindless haters. Some responses and clarifications are in order.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

1. MobileMe vs. iCloud. I totally agree that Apple has done a fantastic job with change management for this product upgrade, issuing periodic reminders of the transition and setting a long transition period. But I didn't criticize Apple for their change management. I criticized Apple for arbitrarily deciding to make iCloud break if you don't upgrade your desktop OS. I am NOT making that up, as some of the haters have accused.

Apple itself says Snow Leopard won't work with iCloud. An Apple support article spells this point out nicely. Hacks are available (aren't they always?), but the point is this: Apple is telling us that calendar and contact sync will break on iCloud with older versions of OS/X, and that the only service available will be email. Corporate help desks don't do hacks; they want support from the manufacturer.

2. Dock. Yes, it's just a rumor that Apple plans to change the dock connector on the next iPhone, a move that would force customers to replace their iPhone accessories. But enough industry insiders have been talking about it to make me believe it.

[ We don't just criticize Apple. Sometimes we take its products apart. Read Teardown: Inside Apple MacBook Pro. ]

I agree with the comments that the current dock port has been around a long time. I just hope that if/when Apple changes the dock, it delivers the promised value. And if it's all about saving space, why is there enough space for an extra chip on that valuable real estate to prevent knockoff accessories?

Apple has every right to recoup its investment in innovation by protecting its intellectual property. But Apple had better deliver some value, not just obsolescence. A new connector isn't an innovation. But if the new connector is on par with MagSafe, the power cord on my MacBook Air, I'm sold. I don't know how many times I murdered my previous Macs because I tripped over a power cord while doing a presentation and knocked the Mac off the podium.

3. Conflict Of Interest. I don't own stock in Apple or its competitors, despite what the haters surmise. I like Apple's technology enough to have become an enterprise customer a few years ago, but I made that decision for business, not personal, reasons. Some of the haters don't seem to understand this point, because they're responsible only for their own technology.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our online community and information resource for CIOs operating in the global economy.

It's more disturbing when a website whose business model and existence depend on Apple starts flaming InformationWeek and me for daring to have an opinion about Apple in an opinion column. Who has the conflict of interest?

4. Lifecycle. To clarify, one of the reasons I've been drawn to Apple over the years is because of its decent product lifecycles and strong ROI. Arbitrarily forcing customers to update because they've adopted Apple products across the board is causing me to rethink that lifecycle recommendation. When I see a sign that Apple proudly wants its customers to keep using their products as long as they want, I'll gladly recant.

5. Our "Inflammatory" Headline. Some of the haters called the headline on my recent column inflammatory. As you may or may not know, the author of a column or story usually doesn't write the headline. I had suggested "Apple's Planned Obsolescence: Enough Already," which my editors changed to "Apple's Planned Obsolescence: Customer Revolt Brews?" Well, considering my own experience with Apple, and those of some of my peers, a revolt could be brewing.

Finally, as for the haters in general, it's startling to me how blind loyalty to a vendor and product can make folks lose their sense of civility. The Apple-focused website (the one with the real conflict of interest) wrote an insulting headline about our beloved InformationWeek and me, and it encouraged readers, based on pieces of my column it threw to them, to send hate mail. (All 10 of its readers sent me pretty nasty emails.) Whereupon I tried to initiate a conversation with some of those folks based on the facts, and their response was to shout me down.

Some of that vitriol made it to the comments thread underneath my column on InformationWeek.com. It's as if calling me names and questioning my motives make them right. I do want to thank those people who have kept the discourse civil, whether they agree with my point of view or not. You have swayed my opinion on some of the issues, and persuaded me to clarify others, which is the real benefit of an analytical discourse.

Jonathan Feldman is a contributing editor for InformationWeek and director of IT services for a rapidly growing city in North Carolina. Write to him at jf@feldman.org or at @_jfeldman.

At this year's InformationWeek 500 Conference, C-level execs will gather to discuss how they're rewriting the old IT rulebook and accelerating business execution. At the St. Regis Monarch Beach, Dana Point, Calif., Sept. 9-11.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.