Comment Re:Confusing the issue (Score 1) 337
The problem were not Windows on ARM itself. The problems were:
1. It should not have shared the Surface name with something that ran on x86. Instead of Surface Pro and Surface RT, there should be Surface and something else - Slate, Pad, Shift, Slice, whatever.
2. They should have waited at least an extra year and spent all of the budget from the Surface RT version 1 on a wider selection of better applications.
3. The Surface RT version 1 hurt the product name by being underpowered for a late 2012 tablet running Windows, even a stripped down version of Windows: 1366x768 resolution, Tegra 3 processor. The first Surface RT should have been generation 2 - 1920x1080, Tegra 4. But again, even that got a lot of criticism for a lack of a good application selection.
The fundamental concept was fine, the execution was inadequate. Microsoft is desperate to gain a foothold in mobile, and I think they're right to be desperate to get a foothold in mobile. I'm glad they screwed it up - I don't like Google, but I'd rather see the future of mobile devices be based on operating systems that have open source cores (even if Google adds a big proprietary layer on top) than otherwise.
1. It should not have shared the Surface name with something that ran on x86. Instead of Surface Pro and Surface RT, there should be Surface and something else - Slate, Pad, Shift, Slice, whatever.
2. They should have waited at least an extra year and spent all of the budget from the Surface RT version 1 on a wider selection of better applications.
3. The Surface RT version 1 hurt the product name by being underpowered for a late 2012 tablet running Windows, even a stripped down version of Windows: 1366x768 resolution, Tegra 3 processor. The first Surface RT should have been generation 2 - 1920x1080, Tegra 4. But again, even that got a lot of criticism for a lack of a good application selection.
The fundamental concept was fine, the execution was inadequate. Microsoft is desperate to gain a foothold in mobile, and I think they're right to be desperate to get a foothold in mobile. I'm glad they screwed it up - I don't like Google, but I'd rather see the future of mobile devices be based on operating systems that have open source cores (even if Google adds a big proprietary layer on top) than otherwise.