1. How the **** did anyone fly airplanes before Apple released the iPad in 2010? Aviation some how made it 100 years without iPads. Maybe we have become too dependent on technology?
How the **** did anyone travel before Henry Ford produced automobiles starting in 1921? We some how made it eons without automobiles. Maybe we have become too dependent on automobiles and mass transportation?
2. I encourage all of you to start your own software/hardware company, and produce devices used by billions of people in an infinite number of possible ways - and never have a single glitch or issue arise. Seriously: Apple has sold something like 300 million iPads and approaching a billion iPhones. Every single one of those devices is used in a unique way with unique situations and combinations of hardware and software.
"Glitches" are always acceptable and understood to be a part of the accepted risks of using an iPad or any electronic device and associated software. The bottom line is that we all understand and accept that "glitches" may occur. And when this problem first appeared I'm sure everyone was quite understanding - after all, s**t happens, especially when it comes to software.
But what has really aggravated this user community, and what makes that anger so apparent on this thread, is Apple's hubris in taking its time to address the problem. This is not some gamer's remote being rendered useless by this bluetooth glitch, this is people's livelihood and safety being impacted by this glitch. I would even go so far as to say any one of us would probably be fine living with this "glitch", if Apple wouldn't be so controlling of its user environment and would allow a roll back to 8.2. But we are beholden to Apple's whim and there is absolutely nothing whatsoever we can do about it with regards to this "glitch". Apple's official policy regarding the fix and not allowing us to roll back to 8.2 has effectively rendered my iPad useless for the purpose for which I originally purchased it for.
3. I agree it is strange that not one single one of the companies who specialize in specifically GPS devices didn't catch this bug until it was way too late. I mean it is one thing for Apple not to test with every possible GPS device - but it is quite another for the makers of a specific device to not test with iOS updates. When your entire company makes about 3 specific devices - I would think it would be pretty important to test every software update pretty thoroughly.
How do you know that this issue wasn't caught by some companies and that Apple ignored them and released 8.3 anyway? How do you know the last beta version of 8.3 was glitch free but that the final public release of 8.3 didn't incorporate a last-minute change by Apple creating this glitch?
4. I don't really have any skin in the game here.
If you don't have any skin in the game then you probably should look at another, more relevant thread.
I just want to use my iPad with river or bay charts when I go into unfamiliar places.
And there's the reason why you don't and can't empathize with this user community. Floating on a river or bay, drifting with the tides and currents, is quite different than flying an aircraft at 140 MPH or more in congested airspace over densely populated areas.
No biggie, I can manage without it until 8.4 comes out.
Good for you.
But some of the people in this thread have been incredibly vocal about how they feel Apple has personally wronged them in some way. That is just not the case.
I would be willing to bet that not just "some of the people in this thread", but every single one of them, myself included, feels that Apple has in fact wronged them.
This stuff isn't easy folks. We do our best in the industry to prevent things like this, but sometimes they happen.
And every one of us, I'm sure, understands that. As I said before, the issue is not that the glitch occurred, but that Apple is taking its time to address it and, at the same time, has eliminated our ability to fix it ourselves via a roll-back to 8.2. This issue is not about the glitch occurring. It is about Apple's glaring poor customer service regarding this issue. Plain and simple.
This is why no company or group that relies on software ever lets people install updates without first certifying the new version. Its why at work we are often three or four releases behind in software - because it takes us time to certify all of the things we rely on...
And that, my friend, is the first accurate statement you've made, because this is where we, as a user community, are at fault. None of us should have ever upgraded to 8.3 without waiting to obtain feedback from the GPS manufacturers as well as the EFB software companies to ensure all was well before upgrading. Personally, I will never again update my iPad for a good 30 days or more after a new release in order to ensure all bugs, if any, related to my EFB and GPS device are published.
In the final analysis, this issue really is a result of Apple's own success - we've all become so used to "it just works" that we ASSUMED any update would in fact "just work".
