Sure, you can say that *more* bugs should be fixed before a product is released. I won't argue that at all. But a world where any software or hardware platform is "bug free" simply doesn't exist- and it doesn't matter what generation you're from.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Why Are There Bugs?
- Thread starter Resist
- Start date
- Sort by reaction score
- Status
I hate myself for doing this, but you really forced me to. "Hello World"
As for this thread. It SO needs to die. Anyone arguing for bug-free releases has absolutely NO experience in software development. They simply don't understand the hundreds of thousands of lines of code (millions?) that go into something like iOS. It's massive. The teams are HUGE working on the modules. What, you think you can pull everyone into a quick coffee session to work out the bugs? You're delusional!!!
I'm on the same side and you want to argue with me? "Hello World" is the result of a simple print statement, believe me Linux is not bug free.
When was that time? I started building software in 1971 - did I miss that time?
ps - You should probably skip flying commercial aircraft - I'd say you really don't want to know about that software.
Thats easy - iOS 11 isn't at final release yet. That might be 11.0.6, 11.0.7 or some other version that Apple hasn't decided yet.
What you mean is "why are there bugs in the .0/.1/.n release" and that has been answered many times, if you wait for perfect software you will still be waiting.
Every piece of software out there that you consider perfect is actually riddled with bugs in the shape of unforeseen circumstances the code won't cope with if those circumstances arise. Those circumstances haven't arisen yet so they are unknown. They may never arise but they are still there. Because software developers cannot possibly foresee every circumstance they cannot code for it.
World peace would also make for a better world, and all it requires is people simply being nice to each other, yet after thousands of years we are still waiting for it...
[doublepost=1508209823][/doublepost]
Because of reality.
[doublepost=1508209962][/doublepost]
Even that can run into issues depending on what it's written in, where it's executed, what else is going on with the system, etc.
Shipping with bugs isn’t new (the old Commodore 64, a trivially simple machine by iPhone standards, had many, many bugs in the kernal, in the SID sound chip and, infamously for those of us old enough, in the disk drive. Many of these were never fixed in any release) but being willing and able to incrementally fix them is, relatively speaking.
Ahhhhh the Commodore 64. Grew up on that and had literally close to 1000 games for it.
What a machine. Bruce Lee, Paradroid, Wizball and so many others. So many days (usually wasted by typos but never being discouraged) typing in listings from Input magazine and many, many hours spent ripping apart broken Quickshot joysticks to salvage the remaining functioning microswitches to make another Franken-joystick. Good times
Two yearly would be impossible, as they need the updates to cover the new hardware. What grinds my gears is when the bugs apply to their own included apps ...you’d think they’d beta test those at least.
Those defending Apple act like its an individual app that’s causing the issue, when the problem I’m seeing is system-wide! I don’t get how testing could possibly have missed it.
I agree “ testing doesn’t get rid of all the bugs”
Writing them out does though.
[doublepost=1508222025][/doublepost]
I mean, How as a tester can you miss the fact that the compass sticks and crashes, safari sticks, mail sticks, etc...and that’s not to mention third party apps sticking and crashing too. these are staple apps that should point to a larger issue than the apps themselves.
It’s very poor form from Apple.
[doublepost=1508222957][/doublepost]
Merge this: I’m supposed to shell out ONE THOUSAND POUNDS ...That’s £’s buddy ...for an iPX when Apple are trying to murder my poor 6s? I already decided I won’t be upgrading my 2014 MBPro to an Apple device because they’re trying to massacre all of my legacy usb devices, devices I’ve been buying since 1999 ...and now this?
Last edited:
Seems like those "sticks" and crashing issues aren't really there for most, which means that they aren't just some sort of widespread everpresent bugs.
Heh....only the first part was directed at you
I should have put a /s so that was clear.Today I received a reply to my support request email from Navigon - one of the apps that has been sticking and crashing - they said some devices (they didn't say which) were displaying issues, and they're looking into the cause ...In the meantime I should temporarily fix the issue by disabling iCloud integration in the app's settings! I did that and it now behaves as it should. So maybe that's a pointer to where Apple should be looking for their solution.
Context of the reply:
"This error occurs due to the update to iOS 11 and only occurs with some devices. The exact cause is not yet known, so we can only offer a temporary solution.
Please deactivate the use of the iCloud: "Settings - General - iCloud ""
Last edited:
So basically just disabling iCloud completely on the device, or a particular setting within the iCloud settings?
I've disabled it in the Navigon app's settings only. They appear to blame it on the iOS11 update though, not their own app. I've asked them which devices seem to be affected by the bug, but haven't had a response to that question ...yet.
All software has bugs....most likely right now, the wifi router and/or your device has a nasty bug that renders the encrytption of your wifi useless.
The issue here is the bug that bugs you isn't fixed. It was a conscious decision to deliver the software with the defect.
Now maybe the decision making process has changed over the last few years that could be debated. But to say no bugs should be delivered is asinine.
Those are the same statements made by people who think everyone should "code" even if they don't have a logical cell in their brain.
The issue here is the bug that bugs you isn't fixed. It was a conscious decision to deliver the software with the defect.
Now maybe the decision making process has changed over the last few years that could be debated. But to say no bugs should be delivered is asinine.
Those are the same statements made by people who think everyone should "code" even if they don't have a logical cell in their brain.
Apple needs to take the "Yellow Cab" mentality. Yellow Cab kept the same vehicle design for decades, woking out the bugs until the vehicle was basically bullet proof. So, instead of coming out with a new iOS, why not completely fix it prior to moving on with a new one? Has any of their iOS's ever had a version where they got rid of all the bugs before releasing a new one?
No such thing would really exist, as has been pointed out in the thread. And all that would come at the cost of not adding features or changing anything for years, which would lose more and more customers who wouldn't see anything new or different.
- Status