Live data from Hacker News

Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

theverge.com

191–200 of 212 posts

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#191

I don't understand all the hate here. Either it will work well or it won't, and the market will decide if it gets to live or die. For a company with resources like Microsoft that has its fingers in so many corners of the market, this seems like a workable, if inelegant, business strategy. I am much more interested in the technical details of such technology. How are they doing this? Is it pure emulation? JIT transpil…

This is a terrible strategy for technology early adopters and evaluators though. It's once burned, twice shy for a lot of people and Microsoft have burned a lot of people in the last few years by completely yanking the rug from under "supported" products.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#192
post #168

Earlier quoted context omitted.

But as so explained the example given - MS tablet computers or 'pen computing' shows the opposite. The modern Windows Phone OS would never have happened if Apple hadn't brought out the iPhone. They still be iterating on Windows Mobile. They had to throw out every bit if mobile tech they had and go back to square one. That's almost impossible to do on your own initiative if you've already got an existing viable produc…

> throw out every bit if mobile tech they had WP7 run on Windows CE kernel, same as Windows Mobile. It uses embedded version of .NET and Silverlight, both pre-existing. Even the touchscreen friendly UI language (once called Metro) existed before windows phone, the first product was Zune. The only bits they had to throw out is marketing bits, branding, logos, that kind of BS. The tech however is an evolution, not "bac…

Windows Phone 7 was two major versions ago, and its CE base was ditched with WP 10.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#193
post #192

Earlier quoted context omitted.

> throw out every bit if mobile tech they had WP7 run on Windows CE kernel, same as Windows Mobile. It uses embedded version of .NET and Silverlight, both pre-existing. Even the touchscreen friendly UI language (once called Metro) existed before windows phone, the first product was Zune. The only bits they had to throw out is marketing bits, branding, logos, that kind of BS. The tech however is an evolution, not "bac…

Windows Phone 7 was two major versions ago, and its CE base was ditched with WP 10.

That is correct. But you mentioned Windows Mobile, so I presumed by “back to square one” you meant WM 6.5 -> WP 7.0 transition.

They indeed replaced the OS kernel while transitioning from WP7 to WP8.

However, they inherited the rest of tech things from WP7. Both .NET and Silverlight were almost same as in WP7, they released the new non-Silverlight UI platform later with WP 8.1 update. Same applies to GUI design, marketplace and other online services. They even inherited non-tech things as well, i.e. logo and branding.

You see, at no point they were starting things from scratch. Instead, they released new generations of products largely based on the stuff they already had developed and tested.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#194
post #168
post #127

Earlier quoted context omitted.

> If it's really for 5-10 years from now, they should release it in 5-10 years when it's fully baked. You can't go dark and build a product for 5-10 years and then drop it on the market. While you're "baking" for years the market will change around you and you'll find that you built the wrong thing and someone else launched early and took the whole market with iterative improvements. > Poorly thought out, badly imple…

But as so explained the example given - MS tablet computers or 'pen computing' shows the opposite. The modern Windows Phone OS would never have happened if Apple hadn't brought out the iPhone. They still be iterating on Windows Mobile. They had to throw out every bit if mobile tech they had and go back to square one. That's almost impossible to do on your own initiative if you've already got an existing viable produc…

What about the products that won because they released "too" early and iterated? YouTube, Twitter, Windows?

Windows phone is an interesting example for you to choose. Do you imagine that the old Windows Mobile team would have produced an iPhone if they'd just kept working quietly? Of course not. No amount of baking would turn Windows CE into an iPhone or even the current Windows Phone. On the other hand, Android released super early when it felt junky, but they iterated repeatedly and eventually beat Apple in market share.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#195

Earlier quoted context omitted.

Just curious, did you support the Ubuntu Edge effort a couple years back? Why or why not? https://www.indiegogo.com/projects/ubuntu-edge#/ I ask because my perspective is that the convergence effort started a long time ago...perhaps as early as Canonical's original controversial release of the Unity desktop...and these efforts by larger players are more or less followers (albeit higher powered followers with larger m…

I think the opposite. Microsoft has a "legacy" on x86 that its open and standardized. Once it moves to ARM, all bets are off (see surface). I wonder if I'm going to be able to install Linux on a "PC" in ten years

They standardized ARM with UEFI and ACPI. All bets are not off, Secure Boot was defeated :)

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#196

So, Microsoft finally solved the Windows on ARM puzzle. Did it take them more than five years to write an x86 emulator, or did they only decide to try this after Windows RT had failed?

The x86 emulator idea was first tried in 2010 with Drawbridge on Experiment 19.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#197
post #162

I can't wait: C:\Program Files\ C:\Program Files (x86)\ C:\Program Files (ARM)\

I can't wait: C:\Program Files\ C:\Program Files (x86)\ C:\Program Files (ARM)\ C:\Program Files (ARM64)\

On ARM64, C:\Program Files\ is used for native. and the normal (x86) path for WoW.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#198
post #155

Earlier quoted context omitted.

The market for people who care about Linux on a 7" tablet is effectively zero. I'm also pretty sure it supports keyboards. Attaching one permanently and turning it into a 7" laptop would make it unsellable.

Does Android allow you to do any meaningful work? The OS is more of a problem than the form factor. Kindle is for games and Netflix not for homework or doing your taxes.

You can install TurboTax and Microsoft Office on Android (not sure about the Kindle Fire) so you can definitely do homework and taxes on it. Personally I don't want to do either of those on a tablet, but that's due to the small screen moreso than the OS.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#199

So, Microsoft finally solved the Windows on ARM puzzle. Did it take them more than five years to write an x86 emulator, or did they only decide to try this after Windows RT had failed?

I don't consider RT a failure itself... I think the failure was in ignoring legacy application environments and not having dev platforms available for testing/targeting windows rt ahead of time as a .Net build target. If they'd supported a dev box (something like a beefy rpi3 with 2-4gb of ram, and ssd support) and sold that early for developers with windows rt a year ahead of the tablet/convertibles it would have go…

RT has a considerable recompiled software collection right now, it's a bit too late now though, and it requires SecureBoot unlocking to be used.

Re: Microsoft is bringing Windows 10, with desktop app support, to ARM chipsets

#200

I don't understand all the hate here. Either it will work well or it won't, and the market will decide if it gets to live or die. For a company with resources like Microsoft that has its fingers in so many corners of the market, this seems like a workable, if inelegant, business strategy. I am much more interested in the technical details of such technology. How are they doing this? Is it pure emulation? JIT transpil…

Maw, the emulation is for binary-only apps. .NET can already be built to ARM CLR bytecode, or to ARM native/machine code. This is for apps where you don't, and quite possibly never did, have the source.

Is the ARM CLR bytecode different from the x86 one ? Why ?
Post reply on HN