You're the foolish child if you can't see how a 12 year old operating system that was dead out of the box is different from appreciating well-optimized code.
Fresh ones are so fun to play with
In the particular instances that we are discussing at the moment we are looking at the relative performance characteristics of three different operating systems. The overall level of functionality of said systems has massive differences in how they operate and the level of layers of code involved with handling things such as screen transitions. iOS is the most dumbed down, at most having to deal with, in essence, an animated .gif for an icon along with a static background.
When we swap over to Windows based phones we have the addition of monocolor live tiles that require an updated state, but nothing else. On Android we have animated icons, live wallpaper and widgets that all need to have their program states updated in order to draw the next frame. When swapping between two panes with multiple widgets on each you could be waiting on states from ten different programs prior to being able to start a state update on your redraw which is going to be handled on multiple layers before final raster and flip.
Now if I was a retarded monkey that got kicked in the head by a donkey, I may try and compare what the mobile OSs are doing on a UI basis as if they were remotely in the league of being comparable. Alas, I am not. I understand what I am looking at. I am not utterly ignorant to what is happening utilizing the technology I am holding in my hand.
The comparison between WinME and Win7 was not accidental.
Did you go to college hoping to be a programmer and failed to make the cut because of sloppy coding?
No, but I did laugh and belittle the helmet heads that couldn't understand the differences between code loops with orders of magnitudes difference in capabilities.
Dumbing software down isn't an acceptable practice.
Then point out that Windows Phone and iOS aren't acceptable. They *are* dumbed down on a UI level compared to Android. That is a point of fact. I would not be willing to state that you just did due to differing needs. What I'm not dumb enough to do is try and compare the performance of things I know *nothing* about.
Android 2.2 to Android 4.1 shows a massive increase in optimization - no more garbage performance on a device that shouldn't have any trouble.
Along with a massive increase in system requirements. The amount of base RAM, the functionality of the GPU and the performance of the CPU all had to reach a certain level or the code structure wouldn't work. 4.1 swapped to a timed code loop for UI refresh instead of a wait to update state. If the hardware isn't up to par you would have your screen scrolling and half blank on older hardware. This could have also been dealt with by doing things like removing widgets, but I certainly wouldn't have been OK with dumbing down the functionality of the OS to pick up a few fps of smoothness on a task that serves no purpose besides bragging rights.
There are many different ways to approach render states, Apple uses the simplest, MS isn't far off, with Android's being *far* more complex. They could start removing features and get it dumbed down to the point where the render states are trivial to handle much like the other two with performance that would be comparable on older devices. Personally, I'll take the vast improvement in functionality for my uses and deal with a hiccup scrolling through the UI(the horror).