Did Microsoft Simply Run Out of Time On Windows RT?
CWmike writes "Microsoft may have simply run out of time with Windows RT, Directions on Microsoft analyst Michael Cherry said on Friday. Windows RT, the name Microsoft slapped on the OS earlier this week after calling it 'Windows on ARM,' or WOA, for months, is the forked version of Windows 8 designed to run on devices powered by ARM SoCs, or system-on-a-chip. Cherry was referring to gaps in Windows RT's feature set, particularly the lack of 'domain joining,' the ability to connect to a corporate Windows network and the lack of support for Group Policies, one of the ways IT administrators use to manage Windows devices. 'This is pure speculation on my part, but it seems like they had to make a trade-off with Windows RT,' Cherry said. 'What we're hearing now about Windows RT is a function of time and how they wanted the thing to behave. It seems to me that the a key goal was to get battery life decent and keep the weight [of devices] down.' His analysis on RT's chance of success: 'I think you can take Windows RT off the table for enterprises,' he said."
They didn't run out of time on it. They did what they've always done with what they see as "consumer" versions of their OS: they deliberately left out certain network- and enterprise-related functionality.
WinRT does have central administration capabilities, just not as extensive as enterprise editions of Windows.
This is pure speculation on my part
systemd is Roko's Basilisk.
I can't help myself but see Keanu Reeves as Ted saying "woaaa".
I have to disagree that Microsoft ran out of time. They just have an insane insistence that everything must but "Windows" even the Windows model doesn't fit. For style of tablets that compete with the iPad, they don't have to be desktops like Windows or OS X. Yet MS felt that they needed to spend development to shove the tablet model into Windows and label it as Windows 8. If MS focused on creating a new OS just for the tablet, they might have worked out all the enterprise features instead.
To clarify the article, Windows programs will run on Windows RT and Windows 8 but only if written specifically that way. Legacy programs are important to the vast majority of enterprises and are not compatible with Windows RT. So Windows RT was never going to be legacy compatible, why do they need to rewrite the desktop Windows model just to call it all "Windows".
The best use case I can see for Windows 8 hybrid approach is unfortunately something that MS has done in the past but never worked out. Hybrid tablet/laptops would have been great for Windows 8. But there is nothing on the horizon that remotely fits this vision. Intel is pushing for ultrabooks favoring less weight and more power efficiency instead of multi-touch transformable tablets. Seems like MS designed an OS for hardware that doesn't exist and even if it did is a very small percentage of users instead of optimizing for the hardware that is in the near future.
Well, there's spam egg sausage and spam, that's not got much spam in it.
On the contrary, Windows NT ran on MIPS, PowerPC and Dec Alpha back in the day.
Even after Microsoft dropped support for non-Intel architectures with Windows 2000, it was rumoured that they maintained the ports to ensure that they did not break portability.
But the underling OS is portable and has been for 20 years. All the enterprise functionality is user land, written in c or c++ so should be trivial to recompile to ARM.
The world's burning. Moped Jesus spotted on I50. Details at 11.
The fact that the Win RT based devices can't join a domain doesn't matter. In fact, the iPad has never been able to join one and it doesn't seem to be a problem with them. Corporate infrastructures are adapting to support the comsumer based devices being brought in by employees... it's just a simple fact. Corporations save a lot of money when they don't have to buy their employees devices, so the trade offs are worth it.
Bill
It's my Sig and you can't have it. Mine! All Mine!
Remember Windows Vista? Not finished. The finished version is called Windows 7.
This is Microsoft SOP. There is a shipping date, which shall be met. Functionality and bug fixes will be added later depending on what complaints they get in the press.
Weaselmancer
rediculous.
It seems as if Windows 8 for ARM is simply turning in to another Windows CE. That is, it is a fork rather than a direct port of the Windows OS with many unique differences.
Back in the NT 4 days you could sit at a DEC Alpha machine and not even notice you were running on a different architecture until you tried to run an x86 executable. (Even then it could run 16-bit Windows 3.1 via an emulator that visually looked exactly the same as running a 16-bit program on NT 4 x86 and later there was FX32) The point is it had the same functionality as the other ports.
Exactly, you're perfectly explained why the XBox 360 can't join a domain either. They must have run out of time!
I was not aware the Sony PS3 was making huge inroads into enterprises the way the iPad is.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
I think the Vista debacle taught them that simply patching later on down the road won't help the product reputation any (seriously - Apple's growth w/ OSX really took off when Vista released). I also suspect that Microsoft can't afford to have too many turns at saying: "yeah it's a major missing feature, but we can always patch that in later".
This isn't 1999 anymore. There's actual competition out there now, and Microsoft can ill afford to have such a blase' attitude towards the consumer, *or* the enterprise.
Quo usque tandem abutere, Nimbus, patientia nostra?
yea printing from ipad or any ios device sucks
but once I jailbroke my ipod touch and my ipad and use the printing stack on cydia omg it's like night and day, I have 100% total control over printing and can print anything, even using my wireless canon pixma mp560 using the jailbreak app i can tell my canon to print double sided and set all the properties as if i were on my windows desktop adjusting them.
jailbroken idevices is where the real power is at, once i jailbroke my ipod touch and got the new bluetooth stack and program called airblue It gives me full control over the bluetooth in the device, where before apple would only let idevices speak with each other when it came to file transfer idevice to idevice and only specific bluetooth devices such as headsets and gps systems.
but with airblue from cydia on a jailbroken device you get full bluetooth control, I can transfer photos from my LG cell phone to my ipod touch via bluetooth, and can pair with any gps device or even use my cellphone as a gps device. I can also tether internet access using bluetooth now.
So if I'm not near any wifi hotspot, I can use my cellphone as a hotspot with bluetooth, connect my ipad or ipod touch to the cellphone via bluetooth jailbroken app and can use my cellphone as the hotspot to hop online and do whatever.
If apple unlocked their devices they'd be more popular and more powerful... There is no way in hell I'd stay with a walled garden idevice, they are shit on their own.
but jailbroken you can unlock full power of them, hell for fun I even compiled apache on my ipod and installed piratebox, so even when it's in my pocket people can connect to my ipod like a hot spot, they are automatically given a webpage with files they can download, google piratebox :)
It's hard to criticize the iPad. They are making them as fast as they can and selling every one at huge margin. It's just impossible under that condition to make a compelling argument that the product is missing something it really needs. You can't sell more than "all of them".
Help stamp out iliturcy.
It seems to me that the a key goal was to get battery life decent and keep the weight [of devices] down.'
And that's exactly what the priorities should be for portable devices.
His analysis on RT's chance of success: 'I think you can take Windows RT off the table for enterprises,' he said."
Why? Apple's iPad doesn't support the feature set that Cherry describes either, and yet it's become the fastest growing tablet in the enterprise. In fact, it's the only tablet device with any traction in that space at all. Something like 60% of the Fortune 500 have deployed iPad or have a deployment plan in the trial stages. When did that last happen with a piece of technology less than 2 years old?
There are plenty of reasons why I think Microsoft's efforts in tablets won't be successful, but the iPad's success has shown that not supporting a core Windows feature set needn't be one of them.
"We live in a global world" - Harvey Pitt, former Securities and Exchange Commission Chairman
Windows on tablet did not get those features because they require uninterrupted network connectivity with a "mothership" domain controller. What does not happen on handhelds.
The whole "analysis" is a ploy to proclaim Windows on ARM "Enterprise-ready" once Microsoft will figure out how to produce domain support with everything cached on the client. What will eventually happen even though it makes no sense.
In reality, handhelds have to be treated as insecure clients, must allow user flexibility in applications configuration and should never be allowed direct filesystem access, however Windows developers are too dumb to make an equivalent of FUSE, rsync and a package manager. My almost-abandonware Nokia N900 has better "enterprise support" now than those Windows "analysts" (marketing people) can ever imagine.
Contrary to the popular belief, there indeed is no God.
It would be very different, because Linux was written from the ground up by competent engineers with portability in mind. Windows was written by some very competent engineers, and many more with -shall we say - much less competence. In order to port Windows to ARM they have to find every place where an assumption was made about internal representation of data structures, word size, endian-ness, and a host of other issues.
Initially NT was DEC Alpha and x86, but they scrapped Alpha support. The reason is simple. Writing portable code, especially in languages like C and C++ take skill, significant effort, and additional time. Obviously, a company that couldn't be bothered to put the time and effort into develop secure code could not be bothered to invest the effort to make it portable either.
Guns don't kill people; Physics kills people! - John Lithgow as Dick Solomon on Third Rock From The Sun
WinRT/Win8 isn't really "big", "Fat", or "Honking". WinRT by itself is pretty lightweight actually.
- Spryguy
There are three kinds of people in this world: those that can count and those that can't
I thought the OP was griping about corporate use? In a business environment printing is very relevant. Checklists, spreadsheets, labels, maps, directions, notes, instructions, letters, boarding passes, checks, etc. If someone at work could not print, there would be hell to pay in ten minutes. At home what good is checking in for your flight on your iPad if you need to purchase an Airprint compatible multifunction printer just to print you boarding pass? At work we don't purchase color multifunction Airprint compatible consumer printers. We have big ass laser copiers that you need to purchase a $20 app in order to print to (Toshiba) and the apps don't work for shit. My co-workers Windows phone can print to our Toshiba. Sorry, but sometimes you absolutely need to print that one single thing. When you cannot, you realize you are not using a general purpose computer; you are using a useful toy. No matter how useful it is, it cannot compete with the flexibility of a general purpose computer. As another poster pointed out, iPads become more relevant once Jailbroken, so flexibility is not actually an iPad problem, it is an Apple problem.
...even Android hasn't yet found any footing there without the carrier infrastructure that helped it to compete with the iPhone in the smartphone industry...
Since when is 35% market share not "footing"?
When all you have is a hammer, every problem starts to look like a thumb.
Actually according to Inside Windows NT, NT was Intel i860 only, then x86, then MIPs.
Alpha didn't come along until significantly later.
Psh, wow, idiotic MS-bashing ahoy! They've screwed up plenty of things, but portability of the OS is not one of them.
It's been policy, thoughout the entire NT project, to maintain a non-x86 port specificlaly to avoid letting non-portable code in. In the early days it was Alpha, then also things like MIPS and PPC, then Itanium (which, say what you will about it, is extremely far from x86 despite coming from the same company). With MS dropping Itanium support, they moved to ARM as the alternate platform. Then of course there's AMD64, which doesn't even really count (being basically an extension of x86) but does still mean that they can't even make 32-bit assumptions.
Also, I hate to tell you, but you're completely off-base about "Linux was written from the ground up ... with portability in mind." Portability has certainly become a major feature of the Linux kernel in the last few decades, but when it was started it was exclusively focused on the 386. http://en.wikipedia.org/wiki/Linux_kernel Read the text of the comp.os.minix post, and the section under Portability. By comparison, the initial development of the NT kernel explicitly did *not* target x86. http://en.wikipedia.org/wiki/Windows_NT#32-bit_platforms
There's no place I could be, since I've found Serenity...