Irony: iPhone 5S Users Reporting Blue Screen of Death
MojoKid writes "It's been a long time since many have seen a dreaded 'blue screen of death' (BSoD), but it's back and in the most unlikeliest of places. Oddly enough, some Apple iPhone 5S owners are reporting BSoD errors, though they're a little different from the ones you may remember seeing on Windows desktops. Rather than spit out an obscure error code with a generic description, some iPhone 5S devices are suddenly turning blue before automatically restarting. The Numbers app in Apple's iWork suite, a free program with new iPhones, seems to be the primary cause, though BSoD behavior has also been observed in other applications, according to complaints in Apple's support forum."
There is a great deal of evidence to indicate we are no longer capable of advancing software.
It has been remarked that if we built buildings the same way we build software the first woodpecker to come along would destroy civilization.
Take a look around. The government apparently spent $165 million on a web site that doesn't work.
There's no discipline in software development. It's slapped together to meet an artificial deadline. It's considered done if it compiles. It's shoved out into the marketplace so everyone can stuff their pockets and then all the developers are fired to make way for the new employees who will design the next piece of shit.
The only measure of how good software is depends on how shiny and "innovative" the user interface is. What the software actually does is utterly irrelevant.
also an apprenticeship system where you learn from pros in the field with real work. Not some professor reading from a book and / or loads of theory.
Dude's been dead for a couple years now... it might be time to find a new meme.
#DeleteChrome
I would dispute that. I don't recall MS-DOS ever crashing itself. True, programs were allowed such low level access to the PC hardware that they could cause a crash, but MS-DOS itself was rock solid and even program crashes were rare. I'm remembering all of the old demoscene stuff that used weird, undocumented functionality and were still stable.
Apple is worse than Microsoft. People like to slam Windows 9x for being unstable, usually rightfully so, but they forget that the Macs of the time were even worse. By the time OS X came out, MS had Windows NT 4, 2K and XP out, which were all very stable. Since then, every MS OS has been stable, including Vista.
On top of that, Apple freaks out when people want to customize or doing something "out of bounds" with their Mac. Microsoft has always encouraged people to do what they want with Windows.
Apple is the new Microsoft.
Just with a shinier surface.
If you notice, the app keeps speaking until he brings up the new (annoying, IMO) running app overview screen. It then stops despite obviously having text left to speak, he touches the app to bring it in the foreground, and it crashes. My money is on the text-to-speech stopping when the overview is brought up causes a bad state, then when the app comes up it probably checks whether it's running or not, gets bad info, and then goes BOOM. I would put good odds on it being either in the text-to-speech API or in the audio API.
In my own work, I found iOS 7 introduced a major flaw in the audio where it no longer acts appropriately in a particular situation in the background and I had to write a workaround -- a hack, really, but it's the only solution that doesn't require months of work -- in order for my app not to get in a bad state where it can no longer run audio again.