I used to use GNU/Linux on my servers but I had to move to OpenBSD when systemd broke too often. Will Fuchsia eventually run on servers? I like OpenBSD on my servers but it's not a good OS on my laptop. I want to use the same OS on my dev laptop and my servers to make my life as a dev easier. If Fuchsia worked well on both my laptop and my servers then I would consider switching to it.
They didn't SUE. They simply revoked his Developer Cert.
Which is EXACTLY what they SHOULD have done.
Charlie Miller is no fool. One would ASSUME he knows the rules. But instead, he thought he'd be snarky and submit an iOS App that he KNEW violated his Developer Agreement, and then, when the App got Approved, he LEFT IT UP FOR A MONTH, where ANYONE could have downloaded and "learned" from it.
Yeah, he deserved what he got; regardless of how "altruistic" his intentions were (which I believe they actually were).
oh wait... Anyone who has physical access AIN root on any mac dating back to 2002 and it remains unpatched... Yeah definitely unimportant. Nothing to see here. Move along.
Kind Regards,
Tim Cook
While it is true that Macs are long-lived; I would be very surprised to see many G3 Macs still kickin' it in any sort of a production environment, SEVENTEEN years later...
Yeah, one of them was "visionary" enough to have Apple running in about 20 different directions at once (when it wasn't big enough to handle that!), and the other one nearly bankrupted the Company by licensing MacOS and Macintosh ROM code to Third Parties.
Without a visionary in charge, the company cuts corners and is losing major ground in 2018. If I owned Apple stock it'd be sold today.
The best thing that could happen to Apple (and to Apple users) is if Elon Musk took control of Apple without him losing any influence at Tesla or SpaceX.
These companies are a good fit, really. Tesla would have Apple product design power and Apple could benefit from someone clearly on Steve Jobs' visionary and operational level.
Yet the APPLE story is on-point. What is your issue... you a manufacture of real-fake SWISS-ARMY watches, COACH ragbags or warmist, Trotsky-ite news ? Can't get bling-traction without faux-action ? Sluts do love bitching together like Chicago baby-momaz hooting krak.
Really, the court ruling is idiotic. If Amazon cannot book those words, some counterfeiter will. And what permutations, exactly, counts as a misspelling? What about other names, where there are many legitimate spellings?
That said, Amazon has really shot itself in the foot with it's 3rd party marketplace. It is increasingly difficult to sort out the crap, the potential crap, and the legitimate products. Personally, and precisely for this reason, I order a lot less from Amazon than I used to.
This.
And, for example, Apple reportedly did an investigation of all the "Genuine Apple" AC adapters on Amazon, and found something like 90% or more were bootleg, non-Apple parts.
And lest you think they were doing that just to promote sales of their own stuff, they started the investigation because of a rash of Trashed iOS and Mac equipment, where the AC adapter had destroyed the gear.
Flextronics, Bartlett, TN (Before they moved to off of Shelby Drive in Memphis, TN.) Even then the G3 and G4 laptop batteries were like $12 while Apple charged $120 for a replacement. I handled the OS imaging for the east coast schools, with those utterly shit district-locked versions of OSx 10.2.x and would only accept those operating system versions, never to upgrade. That means I had identical hardware which could not run the latest 10.2.x updates, I had about 18 system images to choose from (none of which were labeled by district, and every terminal had a different order for the images, with no means of separation. That means I had to deal with memorizing four different OS imaging stations and each of their actual menu configs. Oh but those were laptops, too, and sometimes they got switched around because some tech needed a quick system to double-check an external device that got sent in, like a firewire drive. Great, now I have to figure it out all over again, meanwhile constantly failing to install the proper OS onto the goddamned laptops because of this.
And the shipments of logic boards from Guadalajara. fucking sand in them. We were having to send 1/3 of the repairs right back to the beginning because the logic boards were fucked. Thanks for outsourcing assembly to Mexico, Steve!
Looks like similar QA standards still happen at Apple today, with the same cheap labor and same cheap-ass parts.
Hey, did you guys ever get rid of that shit Cashmere testing suite?
Sounds like you are a pretty lame technician.
Why would Apple go to ALL the trouble of having to create and maintain separate SKUs for "version-locked" computers? It makes no sense; because not only is it SURE to get Apple booted-OFF the "vendor list" for the next-round of computer purchases, but it actually costs Apple MORE money to keep all the manufacturing, warehousing, shipping and other logistics SEPARATE for those ALLEGED "version-locked" machines!!!
Oh, and as for the "sand in the boxes", EVERYONE, even Apple, occasionally has a supplier go off the leash. Wonder if they are STILL a Supplier for Apple?
Since you are obviously stupid, what I suggest was happening was you were attempting to install OS X with an incorrectly-chosen MACHINE-SPECIFIC Install Disc (grey label) for Panther, rather than using the "Full Retail" (Jaguar-fur-looking label) 10.2 install disc, which would install on ANY system of that time-period capable of running OS X at ALL.
But you and your hack employer obviously didn't bother to find any of that out. Now why Apple had those machine-specific OS X install discs is obviously to reduce piracy. Remember, OS X was selling for $129 retail at that time, and Apple didn't want a gazillion pirate copies of OS X installer discs floating around, killing sales of upgrade discs. In retrospect, it probably was more trouble than it was worth for Apple; but it wasn't that the MACHINES were "version-locked" to a specific version of OS X, it was that the INSTALL DISCS you were using only had Drivers loaded on them for one, or a small group of, models of Macs.
By the way, one of the LEGITIMATE reasons why Apple made those machine-specific Installer-discs was that it reduced the "footprint" of the installed OS. Hard drives were miniscule at that time, and saving a few GB (or even 10s of MBs) by not installing a bunch of Drivers and other Libraries that would NEVER BE USED on a particular machine, the machine-specific installers provided a way for Apple to keep their Installer code as simple (and thus as bug-free) as possible, while providing the user with an OS X install that MAXIMIZED their Hard Drive's free-space.
So, you're SERIOUSLY going to compare Apple's REAL OEM batteries to some slabs of plastic-wrapped aftermarket bacon off of some STILL-UNREFERENCED source on AMAZON?'!?
I'm an apple fan, and their not making the info available right up front, "hey guys, new feature! we call it replicant-survival mode, where the candle which burns half as bright burns... ah whatever you get it, anyway, it is there", was definitely an oversight/bad decision/rubbish.
A lot of people will sensibly think, yeah ok, that feature makes sense, even if there was no way to turn it off. If you have an old phone, you are probably into "conserving" anyway, so it makes lots of sense.
I think Apple realizes NOW, that it should have been more transparent about what their "fix" for the premature shutdown issue was actually doing. My personal opinion was that they expected that their timing changes would be small and relatively infrequent, and so really WOULDN'T be noticed by Users. But then Real Life intervened, and some phones' batteries were bad enough that the temporary throttling WAS noticeable; especially when compared to what performance was AFTER a battery-change...
And the rest is history.
TL;dr
Even big, "evil" corporations make mistakes. Apple is handling this as best as can be expected.
Fuck, you're being obtuse. Up until recently, people thought their best option to a slow phone was a newer $1000 phone, not a $79 repair. People think of battery as operating life, not operating performance. If it reports having juice, it should be at max speed, right?
By hiding this "feature", many people couldn't make an informed decision. Given the new information, how many people would have been happy to replace the battery instead of the phone?
Apple is going to take a beating on new sales because now that this is public, those old, slow ass phones will get a $29 new battery and resold for cheaper than a new phone. The resale market is going to boom and people will not upgrade as often.
Dumbfuck. When you get your battery replaced by Apple, you get your original phone BACK.
Unless you've been smoking near your iPhone. Or farted. Or looked at it wrong. Apple is extremely happy to disclaim any responsibility for repairs. And the reason why the procedure is difficult and labor-intensive = expensive? Because Apple deliberately made it so. Other companies somehow can keep battery replacement easy.
It's simple, they didn't want the users to know about it. It's planned obsolescence.They knew the Lithium batteries would deteriorate after a few hundred charge cycles, ~18-24 months and the software would slow down the phones.
The fact that it was NOT disclosed, tells you about their motive. Sell more hardware.
If that was the real motive, the "slowdown" would have been baked-into iOS 2 rather than iOS 10 or 11.
Instead, the timing of this (no pun) makes it OBVIOUS that the "current spike-spreading" code was added to iOS when Apple said they had a software-fix for the iPhone 6 "shutdown" problem. They just didn't take the infinity amount of time it would take to discover how that fix would affect every single iPhone on the planet, and thus, eventually, someone noticed. But what's clear is that Apple was DEFINITELY NOT "trying to sell new phones". New iPhones have been PLENTY faster year-over-year on their own!
Slashdot Mirror
You can dream, but at the end of the day, lather, rinse repeat and it's still just Apple.
Oh, like no other OS has had the occasional weird permissions issue?
Gimme a break!
I used to use GNU/Linux on my servers but I had to move to OpenBSD when systemd broke too often. Will Fuchsia eventually run on servers? I like OpenBSD on my servers but it's not a good OS on my laptop. I want to use the same OS on my dev laptop and my servers to make my life as a dev easier. If Fuchsia worked well on both my laptop and my servers then I would consider switching to it.
Try this instead:
https://stackoverflow.com/ques...
Stupid. Fucking. Hater. Die Hater, Die!!!
Why the fuck did this get (+5)?
I dunno. Maybe because I was RIGHT.
The bigger question would be why is YOUR post +4 INSIGHTFUL?
WTF "Insight" is there in asking why someone ELSE was modded UP???
Maybe he was referring to Michael Spindler? It would be just as comical...
He did manage to get PowerPC out the door, I guess.
You're right! I forgot ALL about him!!!
Ya they kinda do.
https://www.techdirt.com/articles/20111107/18193216671/find-vulnerability-apple-software-lose-your-license-as-apple-developer.shtml
They didn't SUE. They simply revoked his Developer Cert.
Which is EXACTLY what they SHOULD have done.
Charlie Miller is no fool. One would ASSUME he knows the rules. But instead, he thought he'd be snarky and submit an iOS App that he KNEW violated his Developer Agreement, and then, when the App got Approved, he LEFT IT UP FOR A MONTH, where ANYONE could have downloaded and "learned" from it.
Yeah, he deserved what he got; regardless of how "altruistic" his intentions were (which I believe they actually were).
But he DIDN'T get SUED.
Or you could just log in as "root" no password required.
Exactly. That would work on exactly ONE (minor-revisions) of ONE Major Revision of macOS.
Go back to where you came from, Troll...
oh wait... Anyone who has physical access AIN root on any mac dating back to 2002 and it remains unpatched... Yeah definitely unimportant. Nothing to see here. Move along.
Kind Regards,
Tim Cook
While it is true that Macs are long-lived; I would be very surprised to see many G3 Macs still kickin' it in any sort of a production environment, SEVENTEEN years later...
(Yes, I know it said "Starting with" 2002)...
There hasn't been a visionary in charge there since the early 90s.
What? Gil Ameilio? Or John Sculley, Pepsi man???
https://en.wikipedia.org/wiki/...
https://en.wikipedia.org/wiki/....
Ohhhh Kaaaaayyyy...
Yeah, one of them was "visionary" enough to have Apple running in about 20 different directions at once (when it wasn't big enough to handle that!), and the other one nearly bankrupted the Company by licensing MacOS and Macintosh ROM code to Third Parties.
Yeah, visionaries...
Without a visionary in charge, the company cuts corners and is losing major ground in 2018. If I owned Apple stock it'd be sold today.
The best thing that could happen to Apple (and to Apple users) is if Elon Musk took control of Apple without him losing any influence at Tesla or SpaceX.
These companies are a good fit, really. Tesla would have Apple product design power and Apple could benefit from someone clearly on Steve Jobs' visionary and operational level.
Something like this or similar: https://www.marketwatch.com/st...
Stupid. Fucking. Hater. Die Hater, Die!!!
From TFS, this Vulnerability has likely been around since 2002. Steve Jobs didn't die until late 2011.
So, what in the FUCK does the loss of a "visionary" have to do with this Exploit?
Answer: Abso-lutely FUCKING NOTHING!!!
So, go Hate somewhere else, Moron! We're busy here...
You know, you don't get any extra points for following me round to gainsay every single thing I comment-about
When your mom told you that you're special and that everyone remembers you, she was lying.
Funny, I remember you commenting on many of my Slashdot postings; therefore, I assume you remember me, too.
Or do you have some sort of mental disability?
Yet the APPLE story is on-point. What is your issue ... you a manufacture of real-fake SWISS-ARMY watches, COACH ragbags or warmist, Trotsky-ite news ? Can't get bling-traction without faux-action ? Sluts do love bitching together like Chicago baby-momaz hooting krak.
That is the best AC comment I've read in YEARS!!!
Apple
Congrats, you managed to inject Apple in a story about counterfeit sandals. You beat the Trump or SystemD trolls this time.
Funny that I just KNEW some Slashtard like you would miss the point ENTIRELY.
You know, you don't get any extra points for following me round to gainsay every single thing I comment-about...
Moron.
Really, the court ruling is idiotic. If Amazon cannot book those words, some counterfeiter will. And what permutations, exactly, counts as a misspelling? What about other names, where there are many legitimate spellings?
That said, Amazon has really shot itself in the foot with it's 3rd party marketplace. It is increasingly difficult to sort out the crap, the potential crap, and the legitimate products. Personally, and precisely for this reason, I order a lot less from Amazon than I used to.
This.
And, for example, Apple reportedly did an investigation of all the "Genuine Apple" AC adapters on Amazon, and found something like 90% or more were bootleg, non-Apple parts.
And lest you think they were doing that just to promote sales of their own stuff, they started the investigation because of a rash of Trashed iOS and Mac equipment, where the AC adapter had destroyed the gear.
Flextronics, Bartlett, TN (Before they moved to off of Shelby Drive in Memphis, TN.) Even then the G3 and G4 laptop batteries were like $12 while Apple charged $120 for a replacement. I handled the OS imaging for the east coast schools, with those utterly shit district-locked versions of OSx 10.2.x and would only accept those operating system versions, never to upgrade. That means I had identical hardware which could not run the latest 10.2.x updates, I had about 18 system images to choose from (none of which were labeled by district, and every terminal had a different order for the images, with no means of separation. That means I had to deal with memorizing four different OS imaging stations and each of their actual menu configs. Oh but those were laptops, too, and sometimes they got switched around because some tech needed a quick system to double-check an external device that got sent in, like a firewire drive. Great, now I have to figure it out all over again, meanwhile constantly failing to install the proper OS onto the goddamned laptops because of this.
And the shipments of logic boards from Guadalajara. fucking sand in them. We were having to send 1/3 of the repairs right back to the beginning because the logic boards were fucked. Thanks for outsourcing assembly to Mexico, Steve!
Looks like similar QA standards still happen at Apple today, with the same cheap labor and same cheap-ass parts.
Hey, did you guys ever get rid of that shit Cashmere testing suite?
Sounds like you are a pretty lame technician.
Why would Apple go to ALL the trouble of having to create and maintain separate SKUs for "version-locked" computers? It makes no sense; because not only is it SURE to get Apple booted-OFF the "vendor list" for the next-round of computer purchases, but it actually costs Apple MORE money to keep all the manufacturing, warehousing, shipping and other logistics SEPARATE for those ALLEGED "version-locked" machines!!!
Oh, and as for the "sand in the boxes", EVERYONE, even Apple, occasionally has a supplier go off the leash. Wonder if they are STILL a Supplier for Apple?
Since you are obviously stupid, what I suggest was happening was you were attempting to install OS X with an incorrectly-chosen MACHINE-SPECIFIC Install Disc (grey label) for Panther, rather than using the "Full Retail" (Jaguar-fur-looking label) 10.2 install disc, which would install on ANY system of that time-period capable of running OS X at ALL.
But you and your hack employer obviously didn't bother to find any of that out. Now why Apple had those machine-specific OS X install discs is obviously to reduce piracy. Remember, OS X was selling for $129 retail at that time, and Apple didn't want a gazillion pirate copies of OS X installer discs floating around, killing sales of upgrade discs. In retrospect, it probably was more trouble than it was worth for Apple; but it wasn't that the MACHINES were "version-locked" to a specific version of OS X, it was that the INSTALL DISCS you were using only had Drivers loaded on them for one, or a small group of, models of Macs.
By the way, one of the LEGITIMATE reasons why Apple made those machine-specific Installer-discs was that it reduced the "footprint" of the installed OS. Hard drives were miniscule at that time, and saving a few GB (or even 10s of MBs) by not installing a bunch of Drivers and other Libraries that would NEVER BE USED on a particular machine, the machine-specific installers provided a way for Apple to keep their Installer code as simple (and thus as bug-free) as possible, while providing the user with an OS X install that MAXIMIZED their Hard Drive's free-space.
Your straw-man is on fire.
No "straw man" here.
The quality of the battery is ABSOLUTELY germane to this discussion.
Grow up.
Source: apple.com, Amazon.com
So, you're SERIOUSLY going to compare Apple's REAL OEM batteries to some slabs of plastic-wrapped aftermarket bacon off of some STILL-UNREFERENCED source on AMAZON?'!?
Got it!
I'm an apple fan, and their not making the info available right up front, "hey guys, new feature! we call it replicant-survival mode, where the candle which burns half as bright burns... ah whatever you get it, anyway, it is there", was definitely an oversight/bad decision/rubbish.
A lot of people will sensibly think, yeah ok, that feature makes sense, even if there was no way to turn it off. If you have an old phone, you are probably into "conserving" anyway, so it makes lots of sense.
I think Apple realizes NOW, that it should have been more transparent about what their "fix" for the premature shutdown issue was actually doing. My personal opinion was that they expected that their timing changes would be small and relatively infrequent, and so really WOULDN'T be noticed by Users. But then Real Life intervened, and some phones' batteries were bad enough that the temporary throttling WAS noticeable; especially when compared to what performance was AFTER a battery-change...
And the rest is history.
TL;dr
Even big, "evil" corporations make mistakes. Apple is handling this as best as can be expected.
Fuck, you're being obtuse. Up until recently, people thought their best option to a slow phone was a newer $1000 phone, not a $79 repair. People think of battery as operating life, not operating performance. If it reports having juice, it should be at max speed, right?
By hiding this "feature", many people couldn't make an informed decision. Given the new information, how many people would have been happy to replace the battery instead of the phone?
Apple is going to take a beating on new sales because now that this is public, those old, slow ass phones will get a $29 new battery and resold for cheaper than a new phone. The resale market is going to boom and people will not upgrade as often.
Dumbfuck. When you get your battery replaced by Apple, you get your original phone BACK.
Unless you've been smoking near your iPhone. Or farted. Or looked at it wrong. Apple is extremely happy to disclaim any responsibility for repairs. And the reason why the procedure is difficult and labor-intensive = expensive? Because Apple deliberately made it so. Other companies somehow can keep battery replacement easy.
Prove it.
Oh, so now it only costs twice as much as other phones' batteries... until the price cut expires in a year.
Sounds about as good as the Republican tax plan.
Prove it"
the non-apology.
a chance to give apple more money!
Oh, boy!
$30 rather than $1k for a new phone.
Apple sure are some evil geniuses...
It's simple, they didn't want the users to know about it. It's planned obsolescence.They knew the Lithium batteries would deteriorate after a few hundred charge cycles, ~18-24 months and the software would slow down the phones.
The fact that it was NOT disclosed, tells you about their motive. Sell more hardware.
If that was the real motive, the "slowdown" would have been baked-into iOS 2 rather than iOS 10 or 11.
Instead, the timing of this (no pun) makes it OBVIOUS that the "current spike-spreading" code was added to iOS when Apple said they had a software-fix for the iPhone 6 "shutdown" problem. They just didn't take the infinity amount of time it would take to discover how that fix would affect every single iPhone on the planet, and thus, eventually, someone noticed. But what's clear is that Apple was DEFINITELY NOT "trying to sell new phones". New iPhones have been PLENTY faster year-over-year on their own!
https://www.iphonebenchmark.ne...
And lest you think that those recent performance figures are in any way ho-hum compared with the competition, read this:
https://www.cultofmac.com/4626...
http://appleinsider.com/articl...
https://www.tomsguide.com/us/i...
So, Apple doesn't HAVE to slow down their older phones to "make their new phones seem faster." They ARE faster (and also fastEST!)
Simple real-world math: Apple pays about $5 for the battery itself. There's a $24 profit margin.
Why, yes the BOM on the battery is pretty easy to get if you just Google the fucking numbers on the cells.
Someone ban this dipshit fuckwit already.
Prove it, or STFU.
Your move.
Spoken like a true idiot that doesn't know Apple uses the exact same $4 'knock-off' batteries.
Come back when you've actually worked the repair lines like I have, you fuckwit.
You've worked IN an Apple authorized Service center. Prove it.
And you can buy a full replacement battery kit for $25 from third parties.
Apple isn't doing their customers any kind of favor with this.
For $4, you get the repair done by someone who does it five times each week, plus a 90-day warranty.
Where?