The last time Hackerfall tried to access this page, it returned a not found error. A cached version of the page is below, or clickhereto continue anyway

iPhone performance benchmarks after Spectre security update | Melv1n

Apple released iOS 11.2.2 update to address Spectre security issues. I was curious about the actual performance change. So I’ve benchmarked my iPhone before and after the security fix. Here are the results side-by-side to give you a clear view how the performance has changed due to the Spectre vulnerability.

Update: why I removed my benchmarks

I mostly share my knowledge on this site about my experience in technical product management. I updated to 11.2.2 solely for security purposes which I found mandatory patching the Spectre vulnerability. I shared my iPhone benchmarks just out of my own amazement about the numbers. That was it, those were just my benchmarks. Apparently some took it as an absolute truth for others (which I clearly stated it was my own device only) and presented it that way on other sites without any nuance.

The attention was overwhelming with a lot of good folks debating and some negatives (which is ok, criticism is good). Even if you didn’t agree, thought the numbers were bogus or even fake, that’s OK too. You’re entitled to your own view, do your own benchmarks and should always be skeptic.

I linked to other articles and my original scorecard benchmarks to give the most complete possible perspective. Even with the battery debate raging, which I admitted I wasn’t aware of properly at first and added this info appropriately based on the feedback. Fair criticism deserves a response and including that in the article was the right thing to do. I can miss things too.

A personal thank you to all you readers who gave me feedback and kept the discussion classy.

To those who thought I was an Apple hater: I’m Apple-only for 15+ years and my first startup ended up being an agency for iPhone apps. So surprisingly to some of you: I’m the exact opposite of that.

I’m not a professional writer. I write on my personal domain name, with my full name linked and by site info personally traceable because I always believe transparency is the way to go. Everyone should be able to publish and debate openly even when things get heated.

But tonight (15th of January 2018) it just crossed the line…

The main reason why I removed my piece: serious personal threats to my address.

I’m not sure why an iPhone discussion can ignite such anger in a person (or possibly multiple) to consider or expose a very detailed desire to harm them personally and contact through a private channel. I’m not going to accept such threats over any iPhone, battery or anything related debate. This just went too far.I hope you as a reader can understand such a degree of personal attack isn’t worth continuing a debate that seems to be getting out-of-control.

In the end, I think we all agree we want this debate to be solved by Apple giving clarity about any battery/security update issues some devices may encounter so we can keep enjoying the device we all love.

I’m not backing down on writing. I’ll still continue writing about my work experience in product to share knowledge which I still love to do for those who are following my PM articles.

And please remember: please update to iOS 11.2.2 to keep your device safe from the Spectre bug which can lead to data theft or worse. If there was one take-away, this one should be it.

Want to improve your product management?

Be the first to receiveMelv1n'slatest product managementguides and tips.

You have Successfully Subscribed!

Continue reading on melv1n.com