Maids a milking
Seems like both MS and Apple are having some V8 problems. Just wait ill they get to 13.
Apple on Wednesday released iOS 8.0.1 and then quickly recalled it – after people complained the "update" had broken cellular connections and Touch ID. The bungled release was supposed to fix bugs in version 8 of the operating system, which was released this month, including problems that delayed the rollout of its broken …
As if "Your're holding it wrong 2.0" isn't enough.
Pay more for the superior Apple user experience. Now that's what I call Thinking fucking Different.
Seems to me like Apple's problems are outnumbering Microsoft's right now. Microsoft have just gone in an undesirable direction; Apple appear to have had trouble getting a fully-working piece of software out the door to meet their hardware deadlines.
Heads should roll, but don't ask me in which department. Was it an unrealistic deadline or was the realistic deadline simply handled poorly? So heads probably won't roll.
Apple needs to get rid of the yearly OS schedule, OS X isn't much better and has had issues since Snow Leopard. When you run into a big bug/issue (with OS X) there is no hope it will be fixed in the current version, all you can hope for is that the next major release fixes it.
Apple appear to have had trouble getting a fully-working piece of software out the door to meet their hardware deadlines.
Judging on how that sticky-out lens camera lens cover on the back of the iPhone 6 looks like an tacked-on solution to an unexpectedly large component within, I'd say that Apple appear to have had trouble getting a fully-working combination of hardware AND software out the door to meet their marketing deadlines
I dislike both Apple and microsoft, but I have to say that Microsoft does know how to write software which does not break. All Apple had to do was fix a small issue in what is tiny compared to Windows, and has limited functionality compared to windows which for one thing runs on a plethora of platforms, and can attach hundreds of i/o devices.
And they screw it up
And as it happens, the new iPhone 6 ad is out now.
It probably doesn't matter. From what I've seen most of the early adopters were doing a publicity stunt, line sitting for resellers or bought them to "test" the iPhone's resistance to various dunks, drops and bullets. I haven't personally seen anyone actually using the new iPhone either live or on video.
I ordered mine on Friday (from EE) and it turned up on Monday. Actually they tried to deliver it on Saturday. Been using it all week. My minimum contract term ended in July so rather than get a 5S I thought I'd hold out for the 6. It's OK but I'm not impressed with the camera sticking out of the back or the back cover in general -- I thought the zenith was reached with the glass-backed 4/4S.
.. I never install it first, or buy new hardware first.
It's the one trick that works across all platforms and across all operating systems and other software: patience. I know it's old fashioned in a world of instant gratification, but /ever/ so useful :)
So, early upgraders of all ilk, you're not impressing me.
To borrow a phrase, I fart in your general direction.
I've always followed the same philosophy, waiting a time before installing a release. They only came along once a year and it was easy to wait a couple of months to see what bugs got flushed out.
More and more developers are releasing smaller but more frequent releases - I hate the word agile, its not agile, its lazy and poor development practise not interested in producing well written and well tested code first time - "fuck it, the users will test it and we can fix it quickly".
So the time between releases is shortened, and as a user I need to test more often. This ultimately costs me more time and money overall since there are more releases. Every release carries the potential to break something, and all we're doing is increasing that risk, this being a perfect example (and I'm not just getting at Apple, almost all developers are doing it).
There are a few good developers out there working properly and in an agile manner. But being agile requires a much stronger discipline than traditional development cycles, something lacking in many development houses and teams.
More and more developers are releasing smaller but more frequent releases - I hate the word agile, its not agile, its lazy and poor development practise not interested in producing well written and well tested code first time - "fuck it, the users will test it and we can fix it quickly".
Yup. It moves the testing phase of development out to the users, who both get to pay early for the privilege and to suffer the problems of shoddy code. It moves the risk from the software developer to the customer.
I blame Microsoft for this - they discovered they could get away with this with production code, and have been doing it ever since because it saves them both development time (thus costs) and shortens time to market (or, more accurately, time to your money).
BRILLIANT!!! Apple fucks up on their shoddy software and somehow, Microsoft is to blame.
Fanbois, why didn't I see that coming?
First people whinge that nobody acknowledges the brilliant contributions Microsoft has made to the IT world and when we then give them credit for a first people complain again.
There's just no pleasing some people. Sigh :)
sorry, that should have read TSA backdoor - in your new Rimowa suitcase (TSA = Transportation Security-theatre Administration)
personally I use a shapeless backpack, cover it in chicken wire, then put inside a potato sack
(True! - well I did once, long trip around Peru , a nice German suitcase would have worked just as well)
..for another broderline troll article that is fantastic for gently joshing my Apple-loving chums.
As I don't work for an Apple Authorised service outlet any more* I'm only to happy to spread the venom and wind 'em up a bit.
But in all seriousness, getting the update pulled within two hours is pretty impressive (and a gutsy move given it was meant to fix Healthkit IIRC) - it begs the question, what has actually caused this, and how did it get past QA?
Steven 'I support Linux now' R
*although I was never that good at biting my tongue even then, arf
I'm pretty sure I know how it got past QA. Apple doesn't actually consider making phone-calls to be a primary function of these devices, so it wasn't adequately tested. This is also why, I think, they rated so low on call quality for so long.
I honestly think apple considers the "phone" functionality to be a "legacy feature"
You mean the Anandtech review that showed its battery life exceeds that of both the GS5 and Note 3 by over 10% despite a much smaller battery, and the 6 Plus going beyond that by another 20%?
Just because Samsung makes ads claiming that iPhones have battery life issues doesn't make it true.
If you have a phone that can go 10 to 13 hours browsing the web, how exactly are you ever going to run out of battery? I suppose if you're on calls 12 hours a day you might, but I don't see battery life as an issue now and getting additional battery life is irrelevant to me. Being able to swap the battery is even more irrelevant.
If it is a problem for you or you have some sort of paranoid fears of running out of battery, then by all means make sure you have a battery that can be swapped. The idea that someone needs a battery in the 3000 mAh range AND it needs to be swappable is utterly ludicrous to me.
"..for another broderline troll article that is fantastic for gently joshing my Apple-loving chums."
It almost makes me wish I was still on Facebook*. One thing I particularly enjoyed on Facebook was linking to pieces like this, specifically to bring it to the attention of my two Apple-loving brothers.
* Almost.
Of course they have competitive pressure, they have to deliver new innovative functionality to keep abreast of the ever changing mobile market. They absolutely are rushing to market, a) because they have annual deadlines set by the board and b) because the primary target demographic demands change.
It's the same for pretty much all IT product organisations, the market is moving so quickly there has been a shift from the traditional engineering delivery model to a deliver features now and fix problems later method.
The end result is products not fit for purpose.
Would we expect Audi to deliver a new car but the doors don't open, and then accept when they say working doors will come as a service update later on?
Would we expect Audi to deliver a new car but the doors don't open, and then accept when they say working doors will come as a service update later on?
Actually, this accurtately describes an experience my girlfriend and I had with a Peugeot 504 diesel back in the late 70's. The doors failed a total of 9 (count 'em...9!) times before the lemon law kicked in, and the Peugeot got turned into a Subaru
If the same problems happened to other companies with much smaller market-share like HTC, LG, Sony, MS, BlackBerry or Motorola they would suffer a terrible fate... BlackBerry would have to give up the hardware business for good if their new Passport was flimsy and broke within 24 hours or if the phone turned into a useless brick. The blogosphere/twitter/press would be howling.
Not only them with the software updates - Sony have been introducing bugs and disabling key features with updates since they took over the Sony Ericsson bit. My Xperia S was a good example of this.... smartphone with an awesome camera, that post update, wouldn't focus. After a year it was obvious they weren't going to fix it, or the numerous other bugs they introduced, so I sold the thing.
I'm all for Apple getting some stick over this though, and the new iBend feature. Buggy updates were what prompted me to sell my iPhone 3G back in 2010 too.
... now it's fallen a bit. Hope whatever money they saved by not doing more pre-launch testing was worth it. [* casts apprehensive glance at my iPad, which has just upgraded to 8, and hopes '8' is not interweb-speak for 'ate' *]
But to be truthful, that "it just works" claim really meant "you can only do things I choose to let you do". So Apple don't choose to let you make phone calls anymore. Big deal, you still have that shiny new thing you queued for days to get. Bragging rights is all you really want in an iPhone, isn't it?
It does just work, it's just broken. Boo-hoo. People talk here like Apple like robots who can never fall fowl of a mistake when dev'ing their software. Actually, it's high standards they like to upkeep that have let them down. Is that wrong? Nope.
Shame Google don't keep up standards with Android. They should start with their UI for a start before anyone pokes fun at iOS.
going to use Sapphire glass ... to keep the damn thing flat!
Apple used cheap alumin(i)um - they have high strength/tensile alloys but they cost.
But Apple could fix it easily - just make the speaker squeal VERY LOUDLY when someone is squeezing their iThingy too hard.
The Guardian has a pictorial guide on the way Apple should be worn. See: < www.theguardian.com/technology/gallery/2014/sep/24/iphone-6-plus-bending-in-pictures >. It is specifically written for iSheep who also have problems plugging connectors in the right way.
Regarding the Guardian pictorial..
Aside from the "Is that a phone in your pocket or are you just glad to see me?" horrifying fashion pics, it really doesn't look like *any* pocket (save the men's button jacket) is a good way of carrying the device.
How *is* one supposed to carry one about?
Is the man purse, sporran, or cod piece coming back into style for us guys?
...
My sister tucks her windows phone into her brassiere if anyone is interested.
Can't hear it ringing though..
...and this is why I'm not a first adopter of all this new fangled tech ;)
let some other fanbois get all the grief and I'll wait until the fixes are released and then I won't have the apgro.
anyways, back to my Win 3.11 PC and if that fails, my abacus and stonemasons chisel :(
Having seen how well 8.0.0 and 8.0.1 have gone down, I will be using this as a fine example of just why I won't be going to production with your change today, and why testing is important. Perhaps you might just see a small spark in the PHB's eyes when you say "Push it through without testing? You mean like iOS8?"
I feel I should also appologise in public for any complaining I might have made about having to wait for WP8.1.
Sorry!
That's not agile. Agile is about short development iterations, and frequent delivery, true, but not about shipping untested or unfinished product, or about leaving testing to the consumers.
In any case one delivery a year can't be classed as agile. It's just same old same old - delivery date trumped QA, corners were cut and/or testing insufficient.