ORLY?? Coming from a company which has failed miserably to remain competitive in any relevant market other than sub par printers and shitty laptops. I was ecstatic when I heard about HP’s acquisition of Palm and it’s crown jewel; Web OS. The operating system was hands down the best out there in terms of potential (brilliant user interface, terrible hardware and marketing). It’s shortcomings were largely due to negligence and lack of financial backing. If given adequate attention and HP capital muscle, Web OS would have dominated the market. However, HP failed to foster growth in its Web OS division turning a solid platform into the laughing stock of the emerging tablet and smartphone markets. Web OS’ fading into oblivion is a reflection of HP’s management. This guy should be last to make any such judgements. Seriously HP, stick to your crappy printers…

Inclusion of a larger library of drivers is just part of the aspects that makes it more desktop than mobile. While the fact they still need to get more drivers made for ARM and optimized doesn’t negate that advantage. You can still expect a far greater number of devices to just work with RT than either Android or iOS.

You are right though that MS should have made it much more clear of the differences between RT and Windows 8.

XP for example actually needed two Service Pack Release before it really took off and a 3rd before they were done.

Windows 8/RT has yet to get it’s first Service Pack and they can potentially still change quite a bit.

Already, just the regular patches, have apparently dealt with many of the early issues with the MS Surface reportedly acting sluggishly.

While games like Cut the Rope have been shown to lag even a Core i5, which indicates it’s the actual App that needs optimization to run on the OS.

Also, 3rd party have always played a significant role with Windows and Windows 8 is unlikely to be an exception.

Already there are 3rd party UI modifiers for Windows 8 and a pay for one called RetroUI even lets you make the desktop dominant but still use the modern UI.

So we’ll see how it develops over the next few years…

The Intel Celeron is Sandy Bridge based and despite being 1.1GHz it still edges out the Exynos 5 at 1.7GHz as well.

While weight and thickness isn’t as much a issue with a laptop design than it is with tablets because you won’t be holding it all the time.

So the main caveat is the run time difference but the lower cost helps make that more acceptable…

Along with the fact you could always upgrade the drive and RAM, which you could never do on ARM.

So the the Acer Chromebook can appeal to people looking to get a cheap laptop and not necessarily interested in the Chrome OS itself.

I agree though, either way the consumer wins. It’s just a different choice…

The reason RT’s install size is so huge is that they included almost every driver known to man. A huge plus in my book. However, this is also done at fault. Because when I plug my ODB2 sensor into my laptop and it’s detected and I install my drivers, and everything works I’m happy. When I plug my ODB2 sensor into my RT tablet and it can’t tell what the device is or where to find ARM drivers for it … not so much.

Microsoft should have either held this release back OR made extensively sure that people don’t think that this is fully realized Windows 8 in tablet form. However they’re giving people the exact opposite inclination. That’s really my biggest complaint, is that people that aren’t in the know will think this thing can do a lot more than it really can.

They’re optimized to be able to run well on limited hardware after all and that can’t be done while keeping all the functionality and potential features that a much more bloated and harder to run Desktop OS needs.

RT does straddle the area between Mobile and Desktop OS but that still gives it a bit of edge over purely Mobile OS.

Basically there’s a reason why RT install size is over 8x either Android or iOS, and it’s not just because they include MS Office with RT…

Android itself is designed as a mobile OS and that’s not something they can just change, which is why there is such interest in running desktop OS on these mobile devices.

Porting Ubuntu, Fedora, etc. to devices like the Nexus 7 aren’t just for fun but an actual interest in providing solutions that neither Android or iOS can fulfill.

Even Chrome for Android, despite being based on the desktop version, won’t be providing things like Flash support, and it’s a bit more limited than the desktop version in other ways as well because it’s optimized for mobile usage.

So perception is likely to change if RT gets enough time to develop, but we won’t know that for sure for quite awhile yet…

Asus Vivo Tab Smart and Acer’s Iconia W510 both start at $500, just like the MS Surface RT for example.

Specifically, Intel is on record stating they are pushing their low end solutions like Medfield and Clover Trail to be price competitive with ARM.

Both Medfield and Clover Trail are SoCs and use the same LPDDR2 and eMMC as ARM for example.

While the ATOM is still based on 5 year old architecture and the real upgrade starts in the second half of next year when they do both a FAB and architectural update, bringing in technology they already developed for Ivy Bridge to the ATOM and then putting it on a similar 2 year Tick-Tock product cycle from then on.

So it’s not like ARM has nothing to worry about…

But DEVELOPERS will be able to PORT existing software (they some may find useful on a tablet) to winRT.

You are young and like “applets”.. which are cheap truncated pieces of software for mass consumption and marketing. Others don’t even live in that world and are doing their own thing & are prosumers.

WinRT allows for full blown programs on a tablet… not just “apps”.

For the general consumer market though it’s going to take awhile, as right now they’re starting small and just starting to implement things like 64bit memory.

Basically, they should have some final silicon by either the end of 2013 or early 2014 and then 6-12 months later we should start seeing products.

The bulk of the effort will be towards the server and embedded market for now. Switching to 64bit requires adjusting the entire product ecosystem and that’s going to take time.

Things like all the 32bit software isn’t going to go away overnight, demand for 64bit features will need to be developed, and they’re waiting for 20nm and 14nm FAB before they get serious about pushing it.

Barring delays we may see something by the end of 2014 or early 2015, but otherwise it may be 2016-17 if there are any issues along the way… While we’ll also have to see where x86 is by then as well…

I did not say anything about compiling, or installing. I was simply rebuttaling that artard’s misconception that WinRt is just a skin and not a true, full blown OS. Which it is.

WinRT at it’s core is based on the same micro-kernal as WIndows8.

That has NOTHING to do with installing anything on the said device… just that archetectually… Micrsoft built this new OS off of it’s existing kernal. (read the blogs about RT)

WinRT is not anemic and can/could run CAD software.. if a dev ever developed it…

Do you understand…?