For instance, I'd say the tablet experience is more defined by having an SSD than having a touch screen. The hybrid hard drive that has been pushed in the WinTel ecosystem (including ReadyBoost) is a joke.
Customers don't feel minimum latency, mean latency, or median latency. They feel maximum latency. An SSD reduces maximum latency, but half-baked caching schemes don't. Yes, they improve measurable things like boot time, but a quick boot is little solace when your web browser regularly locks up for 20 seconds. (Even if the machine could reboot faster than the time the browser is locked up)
If there was one fundamental tenant of the anti-customer corporate ideology it is "throughput computing", or, the idea that nine woman can produce a baby in one month.
Customers don't perceive throughput, they perceive latency. When you're stuck on the 405 going 5 mph you aren't going to be philosophical and multiply that 5 mph by the density of vehicles, you're going to feel like it's slow for me...
Had the Windows 8 requirements included "no HDD", people would be saying "Wow, Windows 8 is fast!", instead a touch screen adds $100 to the cost, as does the Windows license, so users get shortchanged on the fundamental performance of the machine when they are trying to hit a given price point.
That's really clever. I was very underwhelmed by Windows 8 but I was moving from an SSD-only Windows 7 system, which are still relatively rare. If W8 black-desktoped on a system with less than 1000 IOPS on the system drive the way it does if you have an unsigned driver, there'd be a whole ecosystem of modern hardware and software that can assume fast storage IO opened up, with no backwards compatibility loss at all.
The combination of moving from Win 7 starter to Win 8 (meaning remote desktop and all the goodies get unlocked) and going to an SSD has made it a really awesome machine. Win 8 really does get a lot out of an SSD, but if you hamstring your machine with an HDD or a "Hybrid" Hard Drive it doesn't matter how fast your CPU is if I/O makes the machine go out to lunch.
I'm uncertain they kept cross-platform systems running around (whereas I'm reasonably certain Apple has a full OSX running on ARM internally, as they had OSX/x86 long before they left POWER behind). Although NT was built to support a number of architectures, it's been almost 15 years since NT last ran on non-x86 systems (AlphaNT, the Alpha port of Windows 2000; MIPS and PPC had already been dropped by this time), that's a very long time, and more than enough for x86 dependencies to creep in.
On the other hand, WinRT is supposedly a full NT kernel on ARM, so...
Thus, every version of Windows NT has been released on at least one non-x86 platform.
- NT 3.1-3.5: x86, Alpha, MIPS
- NT 4.0: x86, Alpha, MIPS, PowerPC
- 2000 through 2008 R2 (7.0): x86, Itanium
- 2012 (8.0): x86, ARM
Notice that I listed Windows Server 2008 R2 as 7.0 rather than as 6.1. And that I listed Windows 2000 as 2000, rather than as 5.0.
In other words, I was giving the equivalent workstation OS -- not the internal NT version number.
http://blogs.msdn.com/b/b8/archive/2012/02/09/building-windo...
WinRT is a full NT kernel on ARM so your statement is incorrect. Also, Windows runs on IA64 (Itanium).
With Visual Studio you can currently compile code for IA32, AMD64, IA64 and ARM.
NT is very well done in regard to cross-platform compatibility: all platform specific code is centralized in one location and if you need platform specific instruction, you must you the Hardware Abstraction Layer (HAL).
I've never heard of NT for the i960 before. Are you sure you don't mean the i860? Very different machines.
¹Not that one, this² one.
The i960, on the other hand, had IMHO a great instruction set (even after losing the capabilities¹), with clean orthogonal 3-address instructions combined with programmer-friendly addressing modes.
He's on the Xbox team now. He helped design the OS for Xbone, which, at this point, can't possibly tarnish his reputation that badly.