But it doesn't. Most consumers don't know that Google makes Android. Most probably don't even know that they have an Android per se. Hell, most probably don't know that their phone has an OS. But they sure know that Google is a great search engine.
Because when you have code that calls into a routine in a trusted, internal chip, and that code then crashes, bad things happen? Lots of software would stop working if the chips they're running against stopped supporting all of the instructions the compiler was built against. I'm somewhat amazed that all it did was stop working temporarily instead of corrupting data to be honest.
I can easily imagine that announcing support for 32 bit applications will be discontinued will cause no small number of people to retaliate to this by simply no longer performing or accepting any system updates, because they perceive that their need for that continued functionality is more important than having the latest and greatest that Apple puts out.
And that should be fine. Considering that most 32-bit OSX apps were last built around 2006, most people who were very concerned about legacy compatibility and tested unchanging functionality won't even notice that you can't use an OS released more than 12 years after the application was built.
In fairness though, any apps that are still 32-bit were probably written for much older hardware and would probably run without much difficulty with the additional pointer work.
No, you don't. You can keep running your 20 year old software on a 10 year old OS.
What you can't do is benefit from all the super-modern enhancements for one part of your solution but continue to run older software as a second part of the solution. Nobody, however, is saying that you can't continue to use that solution exactly as it was when you validated and certified it.
apple are telling it to look for a flag only they can set
Which explains how it started working after the 3rd party upgraded their chips, I suppose?
More like the chips were supposed to support functionality that coincidentally wasn't being called prior to the update and was afterwards. The cheaper chips - as cheap chips often do - only supported what they thought the likely feature set was, or the current features used, not the full spec. It happens.
Exactly. Its one thing if the screen was confirming identity, its another thing if a new iOS update was - for free - upgraded and reasonably expecting to use some functionality present in factory chips that wasn't present in the knockoff to provide a better experience. The fact that they can be so easily fixed does seem to imply that the previous chips were just lucky in that the malfunctioning code wasn't being executed.
Yup. I bought a 2016 touch bar model, and it SUCKS. Wish I could have got the previous model, as that was the last worthwhile MBP. If they do this, and basically force everything to go through their App Store, I'm done with them. I guess I'll go Linux, Sure as hell don't want to go back to Windows. And yes, I have a Win10 laptop, for a couple of Win-only apps, and it STILL sucks.
Its not as if the processor choice has anything to do with the application installation policies. I mean, sure, they might choose to do app-store-only at some point (although I personally doubt it), but they could do that on intel or leave things wide open on A14 (or whatever).
Part of this is simply efficiency. With an SPA loaded, clicking on each link to a static article simply sends the relevant data rather than rebuilding the entire page server-side. That's a whole lot faster and cheaper to do.
As for JavaScript being a powerful malware vector, is that really a thing these days?
Sure, in fact that already works today. And as soon as all 911 offices and intermediate phone switches can accept and pass along that information, this problem will be fixed. Until then, however...
Targeted money doesn't work either. For example, in states where all lottery profits go to education (or whatever), they typically just reduce the funding from the general fund by the same amount. Technically everything is "correct", but the end-result is exactly the same as it would be if the earmarked money went into the general fund anyway.
Of course part of that is to disallow this specific situation from happening, where an application took what is arguably too many permissions and buried itself deep into your system.
If you want guaranteed cleanup, you're going to also get some restrictions on how much mess apps can make.
And those are likely to be dismissed - no evidence yet shows any correlation between iOS version and performance scores that's not actually due to a poor battery.
FWIW, I replaced the battery in my 3yo iPhone 6 a few months ago, and it despite heavy use it hadn't dropped enough to trigger the slowdown. It had degraded noticeably from a battery life standpoint though, so well worth replacing regardless.
Agreed. Java is managing to incorporate some of Scala's brevity, to the point that its less compelling.
Additionally, Scala - IMO - went too far. I absolutely loved some fo the ideas, but one benefit of Java for enterprise projects is that you can pick up a Java class written a decade ago by someone you'll never meet and can basically understand it without too much effort. Java's been removing boilerplate slowly but surely over the years in both language points and major libraries; you can write database backed RESTful API servers with 97% business logic these days, which is fine by me. You can write terrible opaque Java code but you really have to work at it.
Scala, on the other hand, did a great job of adding functional capabilities but then also introduced shorthand and overloading to the point where someone who's simply not paying attention can create code that's as readable as high-school Perl scripts. And that's a huge problem for the enterprise.
Google decided to release a product to build goodwill - the featured photos screensaver for OSX. Nice. Its well done, and displays their logo quietly in conference rooms, etc, all over the place.
It doesn't work properly with the most recent release of the OS. They still offer it, it just no longer works, has no support, and has apparently been orphaned.
Now, are they obligated to keep a marketing offering up-to-date? No, of course not, but that kind of attitude even in a simple digital product makes me far less likely to trust them for more expensive goods, whether physical or virtual. What GAE API will be the next to get silently deprecated?
And at the same time, those products were out of reach to many people; lowering the quality to reasonable bounds often resulted in something massively more attainable that only actually breaks marginally more often than the original. Its easy to look at the past with rose colored glasses, but the era of "indestructible" washing machines was also the era of poor people washing clothes by hand and frequent visits from your local washing machine repair man (who could indeed repair the washing machine, but was required to do so far more often).
Same thing when the first iPhone came out and everyone bitched that it wasn't 3G capable - except that nobody else was really working properly over 3G either. Apple just didn't pretend that they were, and when they released the next generation it pretty much "just worked", especially when measured against the competition.
Slashdot Mirror
But it doesn't. Most consumers don't know that Google makes Android. Most probably don't even know that they have an Android per se. Hell, most probably don't know that their phone has an OS. But they sure know that Google is a great search engine.
If it was a carrier problem rather than an OS or manufacturer problem, wouldn't the same issue be affecting iPhones? Because its not...
Because when you have code that calls into a routine in a trusted, internal chip, and that code then crashes, bad things happen? Lots of software would stop working if the chips they're running against stopped supporting all of the instructions the compiler was built against. I'm somewhat amazed that all it did was stop working temporarily instead of corrupting data to be honest.
Maybe they could start having a dialog pop up when you launch them a long time before they're completely unsupported?
I can easily imagine that announcing support for 32 bit applications will be discontinued will cause no small number of people to retaliate to this by simply no longer performing or accepting any system updates, because they perceive that their need for that continued functionality is more important than having the latest and greatest that Apple puts out.
And that should be fine. Considering that most 32-bit OSX apps were last built around 2006, most people who were very concerned about legacy compatibility and tested unchanging functionality won't even notice that you can't use an OS released more than 12 years after the application was built.
In fairness though, any apps that are still 32-bit were probably written for much older hardware and would probably run without much difficulty with the additional pointer work.
I was curious too. My main culprit is WebEx/GlobalMeet - I'm assuming that Cisco can successfully do a 64-bit build at some point.
No, you don't. You can keep running your 20 year old software on a 10 year old OS.
What you can't do is benefit from all the super-modern enhancements for one part of your solution but continue to run older software as a second part of the solution. Nobody, however, is saying that you can't continue to use that solution exactly as it was when you validated and certified it.
apple are telling it to look for a flag only they can set
Which explains how it started working after the 3rd party upgraded their chips, I suppose?
More like the chips were supposed to support functionality that coincidentally wasn't being called prior to the update and was afterwards. The cheaper chips - as cheap chips often do - only supported what they thought the likely feature set was, or the current features used, not the full spec. It happens.
Exactly. Its one thing if the screen was confirming identity, its another thing if a new iOS update was - for free - upgraded and reasonably expecting to use some functionality present in factory chips that wasn't present in the knockoff to provide a better experience. The fact that they can be so easily fixed does seem to imply that the previous chips were just lucky in that the malfunctioning code wasn't being executed.
Yup. I bought a 2016 touch bar model, and it SUCKS. Wish I could have got the previous model, as that was the last worthwhile MBP. If they do this, and basically force everything to go through their App Store, I'm done with them. I guess I'll go Linux, Sure as hell don't want to go back to Windows. And yes, I have a Win10 laptop, for a couple of Win-only apps, and it STILL sucks.
Its not as if the processor choice has anything to do with the application installation policies. I mean, sure, they might choose to do app-store-only at some point (although I personally doubt it), but they could do that on intel or leave things wide open on A14 (or whatever).
Part of this is simply efficiency. With an SPA loaded, clicking on each link to a static article simply sends the relevant data rather than rebuilding the entire page server-side. That's a whole lot faster and cheaper to do.
As for JavaScript being a powerful malware vector, is that really a thing these days?
Sure, in fact that already works today. And as soon as all 911 offices and intermediate phone switches can accept and pass along that information, this problem will be fixed. Until then, however...
Targeted money doesn't work either. For example, in states where all lottery profits go to education (or whatever), they typically just reduce the funding from the general fund by the same amount. Technically everything is "correct", but the end-result is exactly the same as it would be if the earmarked money went into the general fund anyway.
And "Learn More" doesn't tell you what's wrong, it just tells you to download chrome again. Same message in Safari FWIW.
Of course part of that is to disallow this specific situation from happening, where an application took what is arguably too many permissions and buried itself deep into your system.
If you want guaranteed cleanup, you're going to also get some restrictions on how much mess apps can make.
And those are likely to be dismissed - no evidence yet shows any correlation between iOS version and performance scores that's not actually due to a poor battery.
FWIW, I replaced the battery in my 3yo iPhone 6 a few months ago, and it despite heavy use it hadn't dropped enough to trigger the slowdown. It had degraded noticeably from a battery life standpoint though, so well worth replacing regardless.
Jewelry on the secondary market often trades even with or slightly below raw materials value.
No, it's very clearly getting personal enrichment and power through government subsidies and exploiting consumers.
Pretty sure his personal enrichment and power was doing just fine once he'd sold PayPal.
Fails elegantly
And with root authority too!
Yeah, I guess you could call him some kind of tool.
Agreed. Java is managing to incorporate some of Scala's brevity, to the point that its less compelling.
Additionally, Scala - IMO - went too far. I absolutely loved some fo the ideas, but one benefit of Java for enterprise projects is that you can pick up a Java class written a decade ago by someone you'll never meet and can basically understand it without too much effort. Java's been removing boilerplate slowly but surely over the years in both language points and major libraries; you can write database backed RESTful API servers with 97% business logic these days, which is fine by me. You can write terrible opaque Java code but you really have to work at it.
Scala, on the other hand, did a great job of adding functional capabilities but then also introduced shorthand and overloading to the point where someone who's simply not paying attention can create code that's as readable as high-school Perl scripts. And that's a huge problem for the enterprise.
Electrons too these days. Silly case in point:
Google decided to release a product to build goodwill - the featured photos screensaver for OSX. Nice. Its well done, and displays their logo quietly in conference rooms, etc, all over the place.
It doesn't work properly with the most recent release of the OS. They still offer it, it just no longer works, has no support, and has apparently been orphaned.
Now, are they obligated to keep a marketing offering up-to-date? No, of course not, but that kind of attitude even in a simple digital product makes me far less likely to trust them for more expensive goods, whether physical or virtual. What GAE API will be the next to get silently deprecated?
And at the same time, those products were out of reach to many people; lowering the quality to reasonable bounds often resulted in something massively more attainable that only actually breaks marginally more often than the original. Its easy to look at the past with rose colored glasses, but the era of "indestructible" washing machines was also the era of poor people washing clothes by hand and frequent visits from your local washing machine repair man (who could indeed repair the washing machine, but was required to do so far more often).
Same thing when the first iPhone came out and everyone bitched that it wasn't 3G capable - except that nobody else was really working properly over 3G either. Apple just didn't pretend that they were, and when they released the next generation it pretty much "just worked", especially when measured against the competition.