Nottseagull
Well-known member
I keep all of my music in ITunes on my PC.
If I bought an Android phone to replace my current Iphone would that work, or be compatible ?
If they are in .mp3 format, then why shouldn't they?
I keep all of my music in ITunes on my PC.
If I bought an Android phone to replace my current Iphone would that work, or be compatible ?
I remember Microsoft did bring out IE 5 on mac, please correct me if I am wrong?
When you have a closed system like Apple, Microsoft you only go as fast as the developers can push the next operating system out.
And since Android can be installed on many different phones you have your answer.
That doesn't make sense. It's still one development team (Google) versus another (Apple) when it comes to the OS.
What then happens, in Android-land, is that various manufacturers desperately try to find a way to differentiate their super spangly new phone from the 78 other Android phones with almost the same components and same spec.
So what they do is develop their own shit to stick over the top of the vanilla Android. They try and jazz it up a bit. I'm being a little bit unfair - some of the UI bolt-ons aren't bad at all, but plenty are.
It's exactly the same as the PC market of old (maybe it still is - I don't know) where if you bought a PC from a major manufacturer such as HP or Packard Bell etc, you'd find the machine had been loaded up with masses of custom bloatware on top of Windows. In many cases, a complete re-install of Windows was the best thing to do before you even used your new PC.
That's not entirely true. Whilst Android is administered by google, they don't own it and it remains open source. That means you or I could find a bug, fix it off line, submit it to the administrators (google) and if agreed, that fix may very well find itself in the next official release. If google continue to ignore fixes and enhancements recommended or requested by popular demand, then there is nothing stopping another potential administrator taking a cut and moving in it's own direction.That doesn't make sense. It's still one development team (Google) versus another (Apple) when it comes to the OS.
What then happens, in Android-land, is that various manufacturers desperately try to find a way to differentiate their super spangly new phone from the 78 other Android phones with almost the same components and same spec.
So what they do is develop their own shit to stick over the top of the vanilla Android. They try and jazz it up a bit. I'm being a little bit unfair - some of the UI bolt-ons aren't bad at all, but plenty are.
It's exactly the same as the PC market of old (maybe it still is - I don't know) where if you bought a PC from a major manufacturer such as HP or Packard Bell etc, you'd find the machine had been loaded up with masses of custom bloatware on top of Windows. In many cases, a complete re-install of Windows was the best thing to do before you even used your new PC.
only recently moved onto my dads old 3gs he gave me from a blackberry.
have an upgrade in feb, debating the new iphone as essentially those bastards will probably release something by june.
Just get a Windows Phone 7.5 device....blows all this iOS and Android stuff out the water.
Nevertheless, it is more open than Apple's iOS. It should also be pointed out that it absolutely IS open, in that you are able to see the code for the current Android release and all prior releases. Some future branches are also viewable, although there are parts that are kept private. Given that we all have access to current live code, that means potentially millions of eyeballs spotting the current bugs. It's just that you might have no idea whether those bugs are being addressed in a current dev branch or whether you need to report them.I don't think open or otherwise makes any difference. But, for those that do like to bang that drum - it's not really that open at all...
A new way of measuring Openness, from Android to WebKit: The Open Governance Index [Updated] | VisionMobile :: blog
We found Android to be the most “closed” open source project[/b]. In the Open Governance Index, Android scores low with regard to timely access to source code in that the platform does not provide source code to all developers at the same time; it clearly prioritises access to specific developer groups or organisations and has acknowledged this with the delayed release of Honeycomb. Additionally Android scores low with regard to access to developer support mechanisms, publicly available roadmap, transparent decision-making processes, transparency of code contributions process, accessibility to become a committer (in that external parties cannot ‘commit’ code to the project) and constraints regarding go-to-market channels.
Nevertheless, it is more open than Apple's iOS. It should also be pointed out that it absolutely IS open, in that you are able to see the code for the current Android release and all prior releases. Some future branches are also viewable, although there are parts that are kept private. Given that we all have access to current live code, that means potentially millions of eyeballs spotting the current bugs. It's just that you might have no idea whether those bugs are being addressed in a current dev branch or whether you need to report them.
You seem to be pre-supposing that open = good and closed = bad. Is it? Why?
Android source code, the current version of Honeycomb, was not and has not been released. It's been 7 months now. Google's reason as to why is very spurious at best.
Loving your avatar photo!!
That's his breakfast
Anyway. Moving on. To save me actually having to read lots of techy nerd stuff, can someone please explain this Siri thing Apple were on about yesterday, and why it is (or is not) so good?