Al-ibn Kermit
Junior Member
With the kickstand out, can you even tilt the screen? Viewing angle will change a lot between typing on a desk vs your lap.
Anyone know?
With the kickstand out, can you even tilt the screen? Viewing angle will change a lot between typing on a desk vs your lap.
microsoft wants to push developers to developer for the new WinRT runtime.Right but devs could easily recompile them. They can't even do that because RT doesn't have the same OS functionality as 8. I'm saying even if you have source code you can just cross compile because RT is a different OS all together. It doesn't adhere to the same API as far as I can tell from reading.
Right but devs could easily recompile them. They can't even do that because RT doesn't have the same OS functionality as 8. I'm saying even if you have source code you can just cross compile because RT is a different OS all together. It doesn't adhere to the same API as far as I can tell from reading.
Only the runtime environment, which is for both. However, there is functionality that is windows 8 specific.I thought the original idea was that they would be the same API.
I thought the original idea was that they would use the same API.
You're still starting from base 0. You'll still have one OS with a huge library of legacy applications, and another with hardly anything at all.Right but devs could easily recompile them. They can't even do that because RT doesn't have the same OS functionality as 8.
The Windows RT / Windows 8 dichotomy serves MULTIPLE purpose.
And the "why" behind it has to do with the long sordid history that is the "Win32" platform and the various Windows kernels that have supported it, and the ARM based hardware platform that dominates the mobile device market.
It's a little bit complicated.
In a nut shell:
MS basically created an OS for mobile operating systems, they called this OS Windows RT. It's a successor to Windows Phone 7 really, but built to be more usable at a higher resolution on a larger screen.
This OS was designed to run on ARM based hardware.
At the same time, they continued to develop on the Windows 7 OS to create Windows 8. But instead of just doing that, they essentially built a version of WindowsRT into Windows 8. So that any code written for Windows RT, could also run on Windows 8, in it's own UI layer, called Metro UI.
It doesn't work the other way around.. again.. because of the history of these OS's, hardware platforms, etc.
Why? Well.. again, kind of complicated. It's just what MS thought would be a good idea..
The main idea being: get people to use MetroUI apps on PCs and you can hopefully sell a lot of MetroUI based mobile devices and maybe tie this into Xbox and other TV efforts somehow.
They also seem to be hoping touch-screen monitors catch on in the PC / Laptop arena. Making it so you REALLY end up with a Windows RT-like device whether it's Windows RT or Windows 8.
The side benefit: You get tablets that can act like tablets and desktops at the same time.
At least, that's how I see it.. and I think what MS's motivations were.
The motivation wasn't to create a tablet that also acts as a desktop PC. They could have done that at any point with Vista, or Windows 7... there are a wide range of x86 Windows tablets already on the market.
The RT is the metro style apps only.I thought the original idea was that they would use the same API.
I don't know if this has been mentioned, but it looks like the cover comes with the unit.
From MS's website
"Some activities call for a keyboard. Surface comes with an integrated Kickstand and a revolutionary, 3mm thin, pressure sensitive cover that doubles as a fully functioning keyboard and trackpad. Your Touch Cover connects to your Surface with a single magnetic click. Now you can chat with friends and respond to emails comfortably."
The Windows RT / Windows 8 dichotomy serves MULTIPLE purpose.
And the "why" behind it has to do with the long sordid history that is the "Win32" platform and the various Windows kernels that have supported it, and the ARM based hardware platform that dominates the mobile device market.
It's a little bit complicated.
In a nut shell:
MS basically created an OS for mobile operating systems, they called this OS Windows RT.
This OS was designed to run on ARM based hardware.
At the same time, they continued to develop on the Windows 7 OS to create Windows 8. But instead of just doing that, they essentially built a version of WindowsRT into Windows 8. So that any code written for Windows RT, could also run on Windows 8, in it's own UI layer, called Metro UI.
It doesn't work the other way around.. again.. because of the history of these OS's, hardware platforms, etc.
Why? Well.. again, kind of complicated. It's just what MS thought would be a good idea..
The main idea being: get people to use MetroUI apps on PCs and you can hopefully sell a lot of MetroUI based mobile devices and maybe tie this into Xbox and other TV efforts somehow.
They also seem to be hoping touch-screen monitors catch on in the PC / Laptop arena. Making it so you REALLY end up with a Windows RT-like device whether it's Windows RT or Windows 8.
The side benefit: You get tablets that can act like tablets and desktops at the same time.
At least, that's how I see it.. and I think what MS's motivations were.
The motivation wasn't to create a tablet that also acts as a desktop PC. They could have done that at any point with Vista, or Windows 7... there are a wide range of x86 Windows tablets already on the market.
So true Win8 tablets will have there own ecosystem that RT will never see and if Win8 is supposed to be THE Windows tablet os then again, why have RT in the first place?
I think someone in another thread suggested that MS should really jump-start the Metro app marketplace by taking NO percentage of app sales from devs in the first year. They can afford it. Populate the app market first, make it attractive to both consumers and devs, before taking a cut.
What do you mean by tilting the screen? If you meant adjusting the Tablet tilt with the kickstand, it seems possible ..Anyone know?
I'd prop it up on my erection.
Sexy hardware, that.
So true Win8 tablets will have there own ecosystem that RT will never see and if Win8 is supposed to be THE Windows tablet os then again, why have RT in the first place?
nVidiot the other big reasoning seems to be that windows 8 is not really suited for mobile devices when it comes to power and heat. I'm assuming RT is much more targeted in those directions.
the problem with this is that Windows NT and its succesors of XP Vista and 7 have all become increasingly hybridized kernels, but very streamlined in this regard. Windows 8 seems to blow this out of the water and just slaps a whole new kernel onto windows.
Yeah that would be pretty messy.So the Surface comes with the cover? Are we going to see five different SKUs for each? Pro White/Blue/Black/Red/Pink RR White/Blue/Black/Red/Pink?
It's just..built on other platforms (x86,x64), and re-coding it for ARM would be an enormous effort.
So they went the half-way route, and did it the other way around.
Coded an ARM OS and built support for it into their x86 versions.
the metroUI can be used with a mouse and keyboard.Yup.. it's a 2 kernel world now basically.
Pretty interesting as a developer.
But not entirely that different from just having multiple managed runtimes to target. For the "code to the Win32 API" C++ devs it's a bit more of a shock.. but it's not like a lot of those people aren't also experienced Java or .Net devs.. so conceptually it's not really some mindbender.
But is this MetroUI going to really work on PC's? Will there really be some big up-tick in touch-screen laptops and monitor sales or something to help this be usable?
But is this MetroUI going to really work on PC's? Will there really be some big up-tick in touch-screen laptops and monitor sales or something to help this be usable?
What are the iOS and Android equivalents of OneNote and how do they compare?
For business, drawing and education, an active digitizer is extremely useful. Do both versions have an active digitizer? or just the x86/64?
Win8 tablets won't have their own ecosystem. Almost every touch friendly application will be written in WinRT and distributed through the Windows App Store. The "Windows 8" ecosystem isn't a tablet one, it is a desktop one.
What are the iOS and Android equivalents of OneNote and how do they compare?
For business, drawing and education, an active digitizer is extremely useful. Do both versions have an active digitizer? or just the x86/64?
Not just that, running normal desktop apps on a mobile device doesn't seem like they greatest idea if you don't know what you're doing. The Metro environment is built for mobile, providing things like suspended apps, push notifications, limited multitasking. All of which is necessary.
the metroUI can be used with a mouse and keyboard.
there is a one note app on iOSWhat are the iOS and Android equivalents of OneNote and how do they compare?
For business, drawing and education, an active digitizer is extremely useful. Do both versions have an active digitizer? or just the x86/64?
i admit, desktop is still king but the metro ui is still usable. I mostly stick to the desktop though on my....desktop.Exactly why I think the Windows RT tablets will be the main push.
I'm well aware of that.. it's usability has been questioned by many. The mouse experience has been described to me as really awkward.
I need to try it myself.. but downloading Beta OS's is not my favorite Friday night activity.
So true Win8 tablets will have there own ecosystem that RT will never see and if Win8 is supposed to be THE Windows tablet os then again, why have RT in the first place?
Almost every Windows 8 device we've seen has a touch screen
Yup.. it's a 2 kernel world now basically.
Pretty interesting as a developer.
But not entirely that different from just having multiple managed runtimes to target. For the "code to the Win32 API" C++ devs it's a bit more of a shock.. but it's not like a lot of those people aren't also experienced Java or .Net devs.. so conceptually it's not really some mindbender.
But is this MetroUI going to really work on PC's? Will there really be some big up-tick in touch-screen laptops and monitor sales or something to help this be usable?
He's just saying that in context twith only Windows RT tablets, not the other Windows 8 laptops/PCs.
Windows RT tablets won't have access to the Windows 8 ecosystem.
I personally don't think it matters nearly as much as GAF thinks. The iPad is THE proven device on the market right now. It does not attempt to run a "full blown" OS.. that is not what it's 10's of millions of sales are based on.
I could be totally wrong, but you guys are certainly basing your views on some un-proven device, that isn't even a mythical one. Slate based Windows devices have been flopping their way to obscurity for the better part of a decade. I just don't think they are suddenly going to outshine their Windows RT based cousins... just because.. they can function like their Windows RT cousins... for several hundred dollars more.
Exactly why I think the Windows RT tablets will be the main push.
I'm well aware of that.. it's usability has been questioned by many. The mouse experience has been described to me as really awkward.
I need to try it myself.. but downloading Beta OS's is not my favorite Friday night activity.
So the Surface comes with the cover? Are we going to see five different SKUs for each? Pro White/Blue/Black/Red/Pink RT White/Blue/Black/Red/Pink?
e:
Not to mention 64gb 32gb and 128gb 64gb variants, or if they do low end processors too.
Why do the pics make it look so thick
What are the iOS and Android equivalents of OneNote and how do they compare?
For business, drawing and education, an active digitizer is extremely useful. Do both versions have an active digitizer? or just the x86/64?
my main problems with metro on the desktop are basically just for one, no applications and two multi monitor, can only run the Metro UI on one screen at a time.