Slashdot Mirror
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."
Guru Meditation: BSoD.
- In Soviet Korea, only old people loose all their bases to Natalie Portman's petrified hot grits overlords.
Aside from the whole 'a tightly sandboxed "app" taking down the system' thing (which makes one wonder if Apple's apps follow the same rules as everyone else's, or whether there is some Nasty bug in an API), don't iDevices use a totally different design for their screen of death? Macs, certainly, both PPC and Intel, can be made to execute BSOD-level crashes; but the process looks totally different.
Arguably, the sheer lousiness of software is more striking because it (still, despite decades of work and the amount of money riding on some of it) crops up in the face of well heeled customers, whether retail buyers of expensive personal electronics or enterprise/gov buyers who are willing to spend nearly unlimited amounts on their pet contractors...
With buildings, there is plenty of construction that's roughly on the standards of software (Just do an image search for 'Shantytown' if you doubt me...); but structural quality is mostly stratified economically. If you want a building that works, and you have the cash, you can have one. With software, the cities of the world would be a nearly random assortment of mostly shacks, some incrementally nicer than others, with a scattering of structures that were built in 3,000 BC and are in perfect condition, buildings that are constructed from graphene and carbon nanotubes; but have doors made of soggy cardboard stuck to the frame with chewing gum, and other such oddities.
That's the odd thing. Plenty of kinds of engineering are hard and expensive, and sometimes subject to unexpected cost overruns and such; but we've gotten it to the point where if you live in a country with a functional society and fire codes and things, you can buy good buildings, aircraft that don't crash, and other nice things.
With software... your mileage may vary.
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.
Writing good software is an engineering task. As is building bridges, skyscrapers etc...
Unfortunately CS courses are not about teaching software engineering. They're all about teaching the latest fad in computer language and off you go into the marketplace. And lets not even mention of the sunday-day programmers that barely can put 4 lines of code in javascript right.
Put penal/civil responsabilites on those that code, and see how the whole industry changes for the better. Until that time you'll have shitty and not so shitty coders that write shitty code (hint just because it compiles doesn't mean it works correctly) because we ship code as is. It brings down your server room ? Not our fault. Just look at what software companies write in their EULAs. No other industry could do such a thing. We're not responsabile for anything. My ass you're not.
Unfortunately CS courses are not about teaching software engineering.
Of course not. CS is a branch of mathematics. Software Engineering courses teach software engineering. Totally different disciplines.
They're all about teaching the latest fad in computer language and off you go into the marketplace.
No; as above, computer science is mathematics. Air-quote CS air-quote courses taught in community colleges and the like are misnamed, because "introduction to software construction" doesn't stroke the egos of either the teachers or their students.