Linked by Thom Holwerda on Wed 26th Jun 2013 13:03 UTC
PDAs, Cellphones, Wireless "Market trends in Western Europe are not looking good for Apple's iPhone. 'Apple's iOS continues to lose ground as market share declined to 20% from 25% in 1Q12 [first quarter 2012]', IDC said Tuesday. Android, meanwhile, is gaining operating system market share, up 14 percent year-to-year in the first quarter. 'Android continues to dominate the smartphone landscape', according to IDC. In the quarter, Google's OS shipped 21.9 million units and market share increased to 69 percent in the first quarter of 2013 from 55 percent in last years' first quarter." On top of that, Apple got knocked out of the top five in India, where it's also bleeding market share. The America-centred large technology sites that dominate our reporting often fail to spot this huge problem for Apple: the company is only doing well in the US. It's losing everywhere else. And just in case you don't know: 'everywhere else' is 95% of the world, and that's where future growth is to be found. The fact that Apple hasn't addressed this yet is exactly why its shares aren't doing stellar anymore.
Thread beginning with comment 565664
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Why?
by backdoc on Wed 26th Jun 2013 14:30 UTC in reply to "RE: Why?"
backdoc
Member since:
2006-01-14

The java interpreter slows Android down, which yea, makes the OS less smooth. I have seen the S4. So, I know that it's better now that you can get a quad core in a phone. But, the fact that you need a quad core to make it smooth tells you a lot about the problem with Java.

Google used Java to abstract the user space from hardware so that Android would be more portable. They traded portability for smoothness.

I may not have this quite right, but, from what I understand, Ubuntu mostly solves this by promoting HTML5 and QT.

Reply Parent Score: 3

RE[3]: Why?
by radix on Wed 26th Jun 2013 14:38 in reply to "RE[2]: Why?"
radix Member since:
2012-02-07

I wouldn't put so much emphasis on the language/platform. Java execution is actually quite fast, problem usually lies in different things - poor drivers, different approach to multitasking, bad design choices etc. Android performance problems are not reducible to trivial "interpreted bytecode is slow".

I have a hard time imagining that HTML5 + JavaScript will perform better than Java.

Reply Parent Score: 7

RE[3]: Why?
by WorknMan on Wed 26th Jun 2013 17:22 in reply to "RE[2]: Why?"
WorknMan Member since:
2005-11-13

The java interpreter slows Android down, which yea, makes the OS less smooth. I have seen the S4. So, I know that it's better now that you can get a quad core in a phone. But, the fact that you need a quad core to make it smooth tells you a lot about the problem with Java.


As others have said, it's not a Java thing. And trust me... I am no fan of Java ;) Don't compare Android specs to iOS, since iOS has about half the functionality that Android does, and its multitasking isn't as good ;)

As long as you get the right phone and don't download a bunch of crappy apps, performance on Android will be fine. I'd either get a Nexus 4, or wait til later his year and see if a new Nexus is released.

Reply Parent Score: 4

RE[3]: Why?
by moondevil on Wed 26th Jun 2013 19:47 in reply to "RE[2]: Why?"
moondevil Member since:
2005-07-08

First of all how can you guarantee what is written in Java and what is written in C/C++? Unless you go read the code or navigate inside APKs, that is.

Second, although I would prefer a more C++ friendly environment, Android has a JIT since version 2.2 and it offers quite a nice performance.

Reply Parent Score: 4

RE[3]: Why?
by SeeM on Wed 26th Jun 2013 23:10 in reply to "RE[2]: Why?"
SeeM Member since:
2011-09-10

The java interpreter slows Android down, which yea, makes the OS less smooth.


It depends on a programmer. If he/she used complicated xml to design UI, then R.java will beat CPU without mercy. And the UI can be complicated, sometimes with writing xml code by hand. So it's often fault of xml parser, which isn't really it's fault, because parsing text on the fly is always costly.

The problem is: R.java is so neat and everybody loves it. Image hardcoding UI in java for a moment. ;) Now you know why.

iPhone programmers are in better position, since they can hardcode UI to pixels. No worries about actual font, or bitmap size.

Reply Parent Score: 2

RE[4]: Why?
by moondevil on Thu 27th Jun 2013 06:37 in reply to "RE[3]: Why?"
moondevil Member since:
2005-07-08

What?!

There is no parsing happening at runtime, R.java is generated at development time.

Reply Parent Score: 3