More fuel for the fire, I know, but it seems like everyone loves fire right now.
Here's Greg Sullivan, Senior Product manager for Windows Phone talking a bit more about the switch from 7 to 8.
Microsoft: We've only shown you a minority of consumer features in Windows Phone 8 so far - Pocket-lint
"The way we are thinking about this is that Windows Phone 8 is a generational shift that has an associated discontinuity that we don't expect to happen again soon," he said. "The headroom that we get from this new architecture is so significant that it provides us room to grow for a long time."
That headroom is in line with what you see on laptops and tablets today. In theory, Sullivan says, the Windows Phone 8 mobile operating system will be able to support processors with not just dual-core capability, but also those up to 64-cores.
But why the change now rather than three years ago when Windows Phone 7 was announced? Did the Windows Phone team make a mistake? Sullivan doesn't think so.
"We reset our mobile strategy in early 2009 and in late 2010 we delivered a product based on that approach. We went back to the drawing board and started over," Sullivan told us. "We didn't start over from an architecture point of view, but we went very 'low'. It did lots of things, but not what we have today with Windows Phone 8.
"We didn't [go with Windows architecture] because of a couple of dynamics that made it infeasible to do that at the time. The first is that Windows wasn't on ARM at that time. Could the phone team have down it? Yes I suppose, but that work hadn't been done yet.
"The other reason is that the work we've done on Windows Phone 8 and the processors are different in a meaningful way from the previous generation or the ones that we are shipping on today.
"At a risk of over simplifying it, the work on the SOCs [phone processors] today is hierarchy dominated by the modem chip and the apps processor is secondary to it, in the next generation that relationship is reversed and the apps processor is the boss."
But perhaps more importantly for Microsoft, seeing that Apple's iPhone was dominating the smartphone market, and Google's Android platform was starting to get traction, Microsoft didn't want to wait any longer.
"In 2009 it didn't seem a good idea to wait for multi-core processor support," Sullivan rationalises.