Mod Parent UP.

That is EXACTLY it in a nutshell. Perfectly described.

Pretty devious way for someone like the NSA (or a Prince from Nairobi) to get their hooks into your Android.

Shudder...

And, unlike the case with the vast majority of Android Devices, since Apple actually pushes update notices to iOS Devices, there is actually a pretty good chance that yours will be on the list."

And before the haters cry that the latest ssl patch wasn't pushed out to iOS 5 users (or before), remember that the ssl vulnerability came with iOS 6; iOS 5 and before did not have the vulnerability.

So, we should be expecting a similar report from MS regarding iOS, then?

Oh, wait; I said "iOS", right?...

Haven't been watching OS X for the past three or 4 years, right?

I found this in about .5 secs on Google.

But you conveniently fail to mention three very important facts: 1. Apple has brought back nearly all of the capabilities of FCP 7. There isn't a mass-exodus anymore (actually, ther never was. Most FCP 6 or 7 users simply continued to use those versions until FCPX matured), and many Pros have actually switched back. 2. Apple launched a campaign this March, specifically targeted at video professionals, effectively saying "Come on in. FCPX is ready" 3. The recent "paradigm-shift" update to Logic Pro, making it look more like FCPX, has been nearly universally Praised; PARTICULARLY for the fact that all, or nearly all, of the "old features" have been retained, along with the added benefit of the re-factored GUI. So, Apple DOES care about Pros and their Pro Apps, and Apple DOES learn from its mistakes. Now, here comes the ad Hominem attack based on my Username...

No, you know what looks dated: The UI elements in the Windows Modern UI (Windows 8, Ms Server 2012, et al.). I swear it's like they pulled up the Windows 3.1 theme...

Dear Steve, Heard about the reorganization. Sounds great! Keep up the good work! It's visionaries like you that have made Microsoff what it is today. -Tim Cook

Exactly. As an autodidactic embedded dev. With over 3 decades of paid experience, who now has to content myself writing Windows business-apps, THE biggest problem in securing a job that isn't a "handshake deal" is getting past the HR weenie with the buzzword-checklist. If your can't get past that person, you'll never be able to talk to the person that will understand that you can walk the walk...

I'll see that, and raise it to the more effective method of "Don't keep sensitive information anywhere but your brain."

Exactly!

That's why I don't store extensive Contact information in my phone (that's what my personal protein-based storage is for), and ZERO really juicy information. My Apple ID is stored somewhere in the phone, but not my very non-trivial password.

That way, if my phone is lost and compromised, or simply compromised, all the data-thief gets is... wait for it... a PHONE.

BTW, this is also why I don't participate in any of the voluntary data-gathering that is disguised as "social networking". It's bad enough that I have a gmail account; but I don't use that for anything anyone would be able to gain any more interesting information about me than could be gleaned by looking at my grocery-store receipts. And it's bad enough that the last 4 digits of my debit card appears on them...

Bottom line: Stop trusting others' coding and/or algorithmic prowess for your security! Security begins by not storing stuff in places other than your brain. If someone wants to kidnap me and get out the fingernail-pullers, they can have any information they want, and in short order. But absent that, unless someone successfully does a fairly-complicated (I would imagine) MITM attack between my bank's secure website and me, there's little of REAL value that could be gained by examining any of my online data, or by stealing my phone, tablet, work laptop, or home computers. They simply don't HAVE the information. My brain does.

Has my method occasionally caused me inconvenience? You bet! But security and convenience are pretty much mutually exclusive concepts, anyway, right?

Damned no-edit policy...

This page is pretty helpful in that regard.

This page is pretty helpful in that regard.

Not to reply to my own post, but here is a "terminal" script you can run to determine the exact display p/n of your Mac: ioreg -lw0 | grep \"EDID\" | sed "/[^]*/s///" | xxd -p -r | strings -6

Well, on the 15 inch rMBP, the new version of the LG display, p/n LP154WT1-SJA2, (the "2"at the end being the all-important difference), dose NOT seem to exhibit IR; so, I would imagine that similar fixes for the 13 MBP and the iMacs are either in the pipe, or already on store shelves.

Having said all that, I'm not particularly proud of the way Apple has handled this; but I suspect that the Contract Manufacturer, (presumably Foxconn) has a measure of blame in how long this has taken to resolve. That's because CMs tend to but stuff in bulk, and are loathe to throw away "perfectly-good" components, rather than just burning through the old stuff...

That's a BIG 10-4!!! One recent product design I was working on was an industrial motor controller/drive.For the design refresh, I desperately wanted to switch out the venerable 7-seg LED display with a nice graphical OLED display. Had a nice long-life (75 k hrs.) amber monochrome OLED display picked out, was nice and bright, cost was reasonable, display fit in the package, things were looking good...

Unfortunately, these displays typically would be showing a static image for LOOOOONG periods of time. OLEDS had a big time problem with burn-in, and the usual workaround (walk the displayed image slowly around in a small grid of pixels) was simply an attempt to smear the damage over a wider area.

The LCD vendors, however, produced displays that exhibited NO burn-in (but were deemed unsuitable by management, because they weren't nice, lambertian light sources, like LEDs). But I digress...