It's the gesturing capabilities. Capacitive is superior for gesturing, and current Windows tablet OSes aren't designed to take advantage of it.
Aside from the iPad, most tablets on the market don't currently support more than 2 fingers for gesturing globally even if technically, they should support more than 2 simultaneous touches (the iPad supports up to 11). In fact, even on the iPad, global gestures of more than 2 fingers is not enabled by default.
Most apps are also content with just 2 fingers for gesturing. Because you don't need more than 2 to pinch and zoom an article.
Capacitive is superior only in that it's easier to support gestures with more than 2 fingers, but that's it. It's not the magical fix that'll make Windows suddenly 1000x better.
Read the link again...strings like "Microsoft is believed to be working on a common development platform that will unite applications across the TV, desktop and phone did not come from Huang. There are plenty of things we still don't know about Win8. Microsoft never spills all their beans a year (or more) before release. A good example is Kinect: it was released a year ago, people kept asking about Kinect for PC, but MS didn't confirm plans for the PC until today.
They of course would be working on a single common development platform. You know, there's one that already exists: Flash. But that doesn't mean Windows Phone 7 apps are coming to Windows 8 as a fact. It's just a belief.
One reason is that it might not be ready when Win8 comes out. For example, Windows serves every market and almost every language...WP7 serves a handfull. Marketplace team likely will need to have another release as well, and it may not be ready in time.
Or it simply doesn't exist at all, and writing multiple libraries to ensure compatibility is a pain, so they are avoiding that.
Silverlight 5, released a few weeks ago, is in Win8:
http://www.readwriteweb.com/hack/2011/12/silverlight-5-goes-live-no-wor.php so yes, it can be used. End of development does not always equal EOL.
Uh... yes, it does. End of development is EOL. If they don't actively support and update it any longer, then it might well be dead.
Before Windows, Microsoft made their name with tools. There will likely be another SDK...and authors can recompile and re-list their apps. Until they get around to doing that, Marketplace can detect your device, and flag ARM-specific apps so that they don't appear when you access Marketplace with an x86 tablet.
The "apps have to be recompiled to support X platform" worked really well on Android...
Sarcasm aside, even if the tool existed, developers would be less inclined to do it unless there are some substantial benefits to it. The way I look at it, desktop Windows 8 apps would far shadow their mobile counterparts, but at the same time, desktop Win 8 is the majority of the share,
Not a menu button...search button.
Thanks for the correction.
Win8 is NT...WP7 is not. The Windows team is adopting Metro and will design it for screens larger than 4", so there likely would be no need for the three hardware buttons.
The three hardware buttons are almost required to run Windows Phone 7 apps last I checked.
Strategy and excuse are two entirely different things. The original post addresses the fact (a couple of times) that Microsoft has a very capable mobile operating system that they could have used to enter the tablet game over a year ago...but their strategy is to slap Metro on NT instead. And the core meaning being conveyed: what reasoning did they have for going with this strategy?
It's an excuse because otherwise, it's a losing strategy. They are not simply slapping Metro on NT with regards to ARM because ARM doesn't have a desktop mode, or in other words, ARM likely doesn't run on the same NT as x86.
And on x86, Metro is just another interface because there is desktop mode. Slapping an interface on top of another (read: run Windows Media Center all the time) doesn't automagically fix everything.
I would expect to do everything on a Win8 tablet that I can do on my desktop machine or my HTPC, but am restricted from doing on today's mobile devices...so yes, it would be "magically fixed".
Then your beef is more likely with wishing to be able to run Windows on a tablet, and be able to bypass Hulu's silly block rather than with content providers not providing contents for a specific platform.
But in a nutshell, that also doesn't work because with Hulu's aggressive content blocking policy, for instance,
I'm pretty certain they can't detect hardware...nearly all blocking is accomplished by reading the browser UA string, some Flash header string, or in the case of Skyfire the browser itself (Skyfire uses proxy, and proxy gets blocked). So I doubt they would be able to "detect" an x86 tablet.
They may still "detect" any random tablet (not just x86) by checking browser capability and block whenever it reports that the browser supports touch input and multitouch gestures. This is possible in Flash, so if Flash is updated to support x86 Win 8 tablets (and it has been, since I know for sure that multitouch is already incorporated into current Flash), then I'm very sure they can block it.
Since desktop computers don't usually support multitouch, they can get away with saying that only devices with a mouse attached to a keyboard can access Hulu.
So they can still block it if they want to.
[QUOTELet's see...the entire topic is about content, and that content restriction on other tablets is possibly why MS didn't utilize WP7 for tablets. You claimed you could get past the content restriction on an iPad and get Hulu for free. In other words, it IS on-topic. And since you won't back up your claim, I believe I will call bullshit on you.[/QUOTE]
Like I said, believe what you will. Also if my reading comprehension doesn't fail me, the topic is not about how to bypass Hulu blocking, but about how content providers are impeding Microsoft, which you just confirmed.
No, I wasn't. My referral was that your "nightmare" of Atom may end up the same way as the "nightmare" of Prescott ended. Jesus, you even quoted me.
Prescott was only... what? One or two generations?
Atom has stuck around since... a long while ago. It's been two, three generations since then, since the netbooks. There's the difference. And Intel is even gearing up to introduced the forth generation. From my perspective, that means nothing is going to change, at least not next year.
And yet the rumors floating around gadget sites are that Intel's x86-based devices will offer competitive performance and battery life. We'll have to wait at least another six months before we find out.
I have heard that since... 2006. It was always better performance and more battery life, but you know what? Atom in 2006 could achieve 10 hours of battery life, or even more. The problem was that they were mostly in low-cost devices, so manufacturers didn't have the luxury to throw around the high-end components required to make them thinner and lighter (into tablet form factor, if you will). We also had Atom tablets back then (I have one now), but they never took off because they were priced exorbitantly high, and the hardware was extremely limiting.
I can quote real and factual TDP and performance numbers here, instead of just "better performance and battery life". The only way I can see Intel digging themselves out of this pit is to give up and outsource the integrated GPU to PowerVR and the likes instead, since Intel sucks at producing integrated GPUs that don't drain battery and put out more than enough heat to fry eggs. But they tried that, and oddly enough, they don't want to pay PowerVR for proper drivers.
The results? Chips from 2006 still lack proper drivers, and they're all EOL now. Luckily Intel is still "generous" enough to provide drivers to its embedded customers via EMGD, but it's still not 100% operational.
Intel is focusing on Android is more like it. They dropped out of MeeGo if you haven't heard, and MeeGo was in development with them longer than Android even.
Whereas Apple's transition from PowerPC to Intel was six years ago, I wouldn't call that "many years ago". We know that an Intel-based Mac runs XP faster than OS X, but I am unaware of any Windows benchmarks on a PowerPC-based Mac to show that it was faster while running Windows than Intel.
6 years ago is "many" years ago. Technically, PowerPC 970FX (the G5) was more or less on par with high-end Prescott, and with proper optimizations, it could have been almost as fast as Opteron, leaving behind even some of the top Prescott configurations at the time (Xeon 3.6GHz). OSX was poorly optimized, so a number of things were slower.
Anand even had an article about it:
http://www.anandtech.com/show/1702/1
Barring software limitations, the pure performance of the chip clearly surpassed P4 clock-for-clock, and it was approaching Athlon64.