*******************
I have your new sneakers right here.
Posted on 09/14/2016 10:04:47 AM PDT by ImJustAnotherOkie
APPLE RELEASED iOS 10 to iPhone and iPad users on 13 September, but the update turned some devices into overpriced bricks instead of delivering new functionality.
iOS 10 was released to all at 6pm UK time on Tuesday, but those who flocked to install the update were quick to regret their decision.
Just minutes after the rollout began, social media sites filled up with complaints from pissed off iPhone users who, after trying to download iOS 10 over WiFi, found that their iDevice had been rendered useless.
(Excerpt) Read more at theinquirer.net ...
Technical people have pointed out that this limiting charging doesn't seem to be a good fix, Dan. The fires seem to be unrelated to "overcharging" but rather to the phone just being charged not even near fully charged. . . and some have burst into flames not even hooked up to a charger at all. Nor is the problem just limited to the Note 7.
And then there is this...
I can’t say if C# went through this at Version 3. I know there have been some headaches. Did Apple release it too soon (12 years too late)? Or what? Apple has a very very narrow scope in their product line and it’s getting anorexic.
Apple Swift 3: Forward-looking, but not backward-compatible
Another one of your patented lies. Apple makes the iMac in Elk Grove, California, and in a Plant in Cork, Ireland, and the Mac Pro in a factory in Austin, Texas. Apple also makes and publishes software and their Operating Systems for various devices. Apple also makes lots and lots of money.
It wasn’t a lie, just a mistake.
Go to Facebook where your friends are.
Oh, that is just such a problem:
The first is better translation of Objective-C APIs into Swift, meaning that code imported from Objective-C and translated into Swift will be more readable and Swift-like. The bad news is any code previously imported from Objective-C into Swift will not work in Swift 3; it will need to be re-imported.
That is something that is to be expected since Swift-3 has added new functions that re-interprets Objective-C. You expect it to mix the old automatically into the new? Absurd.
It did NOT say it wasn't backward compatible, it says if you want to bring old Swift with Objective-C code in it into the new Swift-3, you'd have to re-import it. IT does not say that such old Swift code would not run if it contained imported Objective-c code, it said that if you were going to continue developing your code, it would not be compatible with the old Swift code you had already developed, to move to coding in Swift-3 if it contained any imported Objective-3, and you'd have to re-import to Objective-C portions to continue coding or modifying the existing code you had already written.
Sometimes making something NOT backwards compatible is absolutely necessary so you can take it forward. This was one of those times. Again, what do you care??? You don't use Swift, any version. Read the articles instead of the headlines. Anorexic? You don't even have a clue what you are talking about.
No, it was and is a lie. You've been told numerous times about Apple's manufacturing of the iMac and Mac Pro in the USA. . . yet you keep repeating your claims of Apple not making anything and not making anything in the USA. Over and over again and I keep calling you on it. . . and you keep making excuses about it being a mistake. How many times do you make such mistakes? YOU are the one who belongs on another website, the one where the other liars such as Liberals hang out.
No problem with the update for jy ipad, (hate the crap that came with it though), the itunes update for my computer took about 10 tries though.
*******************
I have your new sneakers right here.
Sorry, nice try. I haven't worn sneakers for 55 years.
Guys, I work in IT. I have used Apple products since 1986, and MS products nearly as long.
To me, it is all just computers. Ones and zeroes. They do my bidding (when they work) and I don’t do theirs...mostly.
Unless I am woken up in the middle of the night because they aren’t doing my bidding.
Point is, they aren’t much different from a kitchen knife. Some are sharp, some are dull, some cut tomatoes, some cut bread. But as long as they do what I want, then I don’t really care if it has an ivory handle or a wooden one.
As long as they do what I want, I don’t care. We have bigger fish to fry, like figuring out how to save our Republic.
If it can be saved.
Uh, what "extremely annoying everyday prompt to upgrade" is that? I've never seen such a prompt from Apple. Are you referring to the little circle 1 badge on the Settings Icon?
So you’re saying the technical people - with zero inside information about what the cause is - are better judges of solutions than Samsung?
I'm saying that tech people, looking at the conditions and timing present in many of these Samsung phone battery related fires, are concluding they're not much related to igniting at the end of the charging cycle when the battery is fully or over charged. There is no correlation to WHEN in the charge cycle, or even that the phone must be on charge, for the battery to fail catastrophically. So limiting the charge to 60% seems like throwing something against the proverbial wall to merely see if it helps.
At this point, I don't think they know what is causing the problem.
But you're more than willing to spread FUD about "unnamed tech people" claiming that Samsung's solution is wrong.
Got it.
Factual data. Samsung phones are bursting in to flames at unpredictable times, regardless of whether or not they are being charged or not. There were videos of two from today alone on the news, one sitting on a table in a restaurant and another blowing up in a woman's purse on a counter in a store. You cannot tell me or anyone they were being overcharge at the moment they exploded. They were not even connected to a charger. Fact. If that's FUD then the major news agencies are in on it.
This is why warfarin is an effective pesticide against rats. Smart rats don't eat unfamiliar food. They let the dumb rats eat it first. Then they observe and wait. Only if the dumb rats are still alive, do the smart rats partake. That strategy usually works. Except warfarin is slow-acting, so it gets the smart ones along with the dumb ones, the smart rats having prematurely concluded the tasty rat poison is safe.
Of course, the main threat facing us today isn't rats. It's 'Rats! And the head 'Rat is on Coumadin, which is a brand name for warfarin (it has medicinal value as an anticoagulant, which is how, at higher dosages, it kills rodents).
Just a little food for thought. Think before you partake.
Yes plus a pop up everyday telling me an update was available and would I like to install it now or be reminded later.
That disappeared when the new update was released, no notice that a new one is available now.
That was John Mitchell, Nixon's AG (1972): "Katie Graham's gonna get her tit caught in a big fat wringer if that's published", predicting what would happen to the publisher of the Washington Post, if they published a story about a "Secret GOP Fund" that was used to gather information about Democrats.
Bookmark....mine!
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.