v5.0 was a bad update.
but we don't really care because we WANTED it. when we want something, if it causes a bit of pain we talk about it with others and then the apathy of expectation kicks in when we just take it on the chin, we have become used to things failing. like the planet for instance.
we can't through money at something that does operate on the proposal of money, we have to make a mental shift away and check ourselves why we need to consume new stuff.
so iOS5.. . sure, it's got all the bells and whistles that we were wanted but we didn't need it taking out the content on our devices and in my case i have a problem with my iphoto11 crashing every time i try and load and import.
i'm in the studio on a sunday wanting to play catchup mode and my productive mac experience is waning at the moment - it's hard to remember the time when windows was like this all the time.
i guess i've got used to apple normally picking up the ball. on this occasion they have dropped it. like everyone in the world of apple i'm sorry for the loss of steve and his fight against cancer, that's a given.
so let's not make this about steve and the wonders that gentleman bought to the digital world we frequent these days. he made computers do the heavy lifting and gave us devices that just worked.
so what went wrong with this push..
testing basically. developers have had iOS5 betas for months and months so they could integrate features and be ready for this new push no doubt but it's up to us as the users on this occasion to take the hit.
in the grand scheme of things i guess they have gotten away lightly in that we can restore from backups but i'm hearing more and more from people how they have lost contacts and media.
that's not good enough - especially when your talking about iCloud. at this moment in time i'm sitting looking at an iPhoto 11 issue with importing pictures, i try and enable iCloud in the app and it crashes.
basically, my productivity tool is acting like one. it's always at the moment that you need something to work does it decide that it's time to eat the digital dust. i'm really happy to have notifications.
i'm glad they have it baked in like that, but really did we get so used to not having notifications (ok, i used boxcar/push anyway) when other platforms did, was it really hard for apple to drop that walled garden for us to be notified about our actions in our social grids? and this is the triple whammy for me - integrating twitter.
i could go down many avenues with this but i really think that apple did not think this through. are they testing the capacity of twitter, trying to break them or trying to admit that finally twitter is actually going to stay around, do they have vested interests in it - who knows, who cares.
for me the problem lies in the fact that millions of people that were not on twitter finally find it baked into settings. i'm not adverse to more users and more people using a platform that i frequent a lot i'm just surprised that apple pushed all these things at once.
i actually find it quite arrogant that we have this expectation that well, it's more data we can test to see if our scaling is working just to then release a sodding iPhone 4s which nobody can actually activate around the same time!
and now that the world of the crackberry is in the toilet we can expect a bunch of trackball pushing obsessive sms types filling up the iMessage tubes with streams of material.
at least when they were on their own network we had a bit of breathing room. we need independent networks, we need different options.
i for one personally do not want one cloud solution, it has to be multiple methods of input on different carriers to different servers and different clouds - while we are at it let's start really looking at optimising those heat bearing servers and server centres and stop pushing cooling air around.
rant over. you failed me today apple.













take me back to the top. iz lazy to scroll