Slashdot Mirror


Windows 10 On ARM Will Support x86 Apps From Outside the Store (liliputing.com)

An anonymous reader quotes a report from Liliputing: First announced last year, Microsoft provided an update on Windows 10 ARM at the MS Build developer conference today. And the company confirmed that not only would Windows 10 ARM be able to run legacy apps developed for computers with x86 processors but you'd be able to just download any old Win32 app from the internet, install it, and run it on a computer running Windows 10 ARM. In other words, Windows 10 S runs on devices with ARM or x86 processors, but only supports Windows Store apps. Windows 10 ARM only runs on devices with ARM chips... but supports apps from pretty much any source. Developers don't need to convert their software in any way, because Windows 10 ARM includes a built-in emulation layer that allows Win32 apps to run on an ARM-powered system. But Microsoft demonstrated how you could download a common program like 7zip from the internet and simply install it on a device with a Qualcomm Snapdragon 835 processor. Of course, developers can also package software optimized for ARM as Universal Windows Platform apps for distribution in the Windows Store. But they don't necessarily have to.

115 comments

  1. So much for "one Windows"... by Anonymous Coward · · Score: 2, Insightful

    The Windows 10 nightmare continues. I haven't read one single good news about that damn OS ever since it was released. Prior to it, everyone was saying how it was finally gonna bring back the real Windows, but what we got was pure sadism in software form. And it keeps changing around. It's surreal.

    1. Re:So much for "one Windows"... by roc97007 · · Score: 2, Funny

      Ok, here. Read one single good news about that damned OS:

      It's better than Windows 8.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    2. Re:So much for "one Windows"... by ArhcAngel · · Score: 3, Informative

      Well they screwed up by giving it an even number. Everyone knows only the odd numbered Windows are any good.

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    3. Re:So much for "one Windows"... by dreamchaser · · Score: 0

      It sounds like you've never used it. I run it on my gaming rig because, games. It's not bad at all. Far better than Win 8.x and I'd also go so far as to say better than XP or 7.

    4. Re:So much for "one Windows"... by arglebargle_xiv · · Score: 1

      run legacy apps developed for computers with x86 processors

      To understand this sort of stuff you need to translate it from Redmond Newspeak. In this case they're referring to "mainstream apps that everyone uses every day". Contrast with "Windows 10 ARM apps that will be as popular and wildly successful as Windows RT ARM apps were".

    5. Re:So much for "one Windows"... by Anonymous Coward · · Score: 0

      At what category? In the amount of built in spyware? At annoying its users with bland and unintuitive UI?

    6. Re: So much for "one Windows"... by Anonymous Coward · · Score: 0

      Honestly, you guys might hate what's going on, but I see a lot of this as MS finally stepping up their game. Move after move after move set up to make the windows 10 ecosystem more flexible and useful.

      This one move took Windows 10 on ARM from "never never" to "maybe" for a lot of people.

    7. Re:So much for "one Windows"... by Anonymous Coward · · Score: 1

      So it's an excellent Toy OS?

      sad.

    8. Re:So much for "one Windows"... by Anonymous Coward · · Score: 1

      Unintuitive? It's better than windows 8. However it is schizophrenic when it comes to settings. Maybe it's in the settings app, maybe it's in the control panel. But at least you can still find what you're looking for.

      And yes, it's UI might be bland (making win3.1 look interesting!), but that's just them jumping on the flat-and-boring UI design that Jonny Ive introduced with iOS7

      And yes, i do admit, Win10 is terrible. But at least it's better than Vista

    9. Re:So much for "one Windows"... by Immerman · · Score: 3, Funny

      >what we got was pure sadism in software form.

      Exactly! It brought back the real Windows!

      --
      --- Most topics have many sides worth arguing, allow me to take one opposite you.
    10. Re: So much for "one Windows"... by Anonymous Coward · · Score: 0

      And of course going out of its way to lock down what you do with your own hardware, dictate what software you can run (Windows 10 S, take a nice big bow!), and invade your privacy in the EULA (file access), telemetry (gotta love keyloggers and eavesdropping) and forced updates (you'll run the software we want you to, when we want you to!) alike. Never mind the deceptive practices they used to put it on everyone's computer in the first place.

      They're sure stepping up their game alright. At this rate any machine you can actually use as you like instead of as a Microsoft cloud gateway will be extinct on the consumer market in no time, leaving them to, for all practical purposes, own and control every PC you can possibly pay for. Plus if this works out, once all our data is on their cloud, we won't even be able to CONSIDER any alternatives. Won't that be great everyone?

    11. Re:So much for "one Windows"... by Anonymous Coward · · Score: 0

      so 2k=bad and 95=good? fuck off.

    12. Re: So much for "one Windows"... by Anonymous Coward · · Score: 0

      Yup, beginning to look like Apple and Android, along with Linux. All oses make you run their specific type of program. So what's so bad about win10? Keyloggers? On all three. Ads? On all three, specific updates sameo, the difference is, that win supports legacy hardware, the only one different, is Linux. They do the same, support legacy, Apple and Android have definite drop dead dates. No longer support. I may have to look at arm to get support for my four year old tablet, cool.

    13. Re: So much for "one Windows"... by Anonymous Coward · · Score: 0

      You've been trapped in your own echo chamber too long.

      Most people don't get upset about abstract stuff, they get upset that something doesn't work.

      That certainly doesn't bode well for windows 10 s, but it won't be the first or last poor decision that is ultimately immaterial out of MS.

    14. Re: So much for "one Windows"... by Anonymous Coward · · Score: 0

      I wouldn't conflate the shell with the operating system, but Windows 10 has a long way to go before it feels like Windows again.

    15. Re: So much for "one Windows"... by Anonymous Coward · · Score: 0

      And I would say that you are wrong.

    16. Re:So much for "one Windows"... by roc97007 · · Score: 1

      At what category? In the amount of built in spyware? At annoying its users with bland and unintuitive UI?

      Spyware, point. Bland, also point. Apparently Aero was too CPU-intense for tablets. But what made it better than Windows 8 was that someone with Windows 7 and earlier experience could actually use Windows 10 without blowing their brains out. Yes, it was uninspired. Yes, some admin stuff was here and some was over there, where it used to be all in the same place. Yes, it still tried to do some touch-centric stuff entirely inappropriate in a KVM environment. Yes, the live icons in the start menu are really irritating and the first thing many people delete. (At least there *was* a start menu!) But people who just wanted to get their work done (where "their work" != "evaluate new operating systems") could, most of the time, do their work without fighting the operating system.

      I was an early adopter of 8, because we had a laptop with a touch screen and 7 just doesn't do touch very well. (Laughingly bad, actually.) 8 was so frustrating that after a month or so we did a system restore back to 7. (We ended up giving the touchscreen laptop away and going with a Samsung Note, because Microsoft didn't get content creation on a touch screen, and there were tools that worked ok in Android. Microsoft is trying harder now, and Samsung seems to be abandoning content creation, so maybe it's time to switch back.)

      So when 10 came out, I was planning to skip it and see what they came out with afterwards. But the free upgrade to 10 was a strong motivator, so I upgraded an older PC ... and it was ok. Not great, ugly interface, but I could work. (And really, the eye candy of Aero doesn't help me work any faster.) So after careful tests, I bit the bullet and upgraded my main workstation. And it's been ok. I still think the GUI design of 7 is superior. But I can work with 10, whereas, I couldn't with 8.

      I still hesitate to call 10 an "upgrade" over 7, but the good news is, they haven't wrecked it so bad as to make it unusable. The Adobe suite only works on Winders and Mac, and at least this year, I don't have to hemorrhage money and switch to Apple. And become acquainted with the eccentricities of *that* platform.

      So yeah, "one single good news about that damned OS" is that it doesn't quite cross over the line to unusability. At this point in time, I'll take that.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    17. Re:So much for "one Windows"... by Anonymous Coward · · Score: 0

      No, it fucking isn't.

      Windows 8 is Windows 7 with under-the-hood improvements and a shitty start menu, but is perfectly serviceable by installing Classic Shell. Windows 10 is malware garbage.

    18. Re:So much for "one Windows"... by Anonymous Coward · · Score: 0

      2K wasn't a consumer level OS. It was a replacement for Windows NT 4.

      Still, the even/odd "rule" is bullshit. Here is why:

      Windows 1.x - sucks
      Windows 2.x - sucks
      Windows 3.x - sucks
      Windows 95 - sucks
      Windows 98 - sucks
      Windows Me - sucks
      Windows XP - sucked at first, became good with service packs
      Windows Vista - sucked at first, became good with service packs
      Windows 7 - good (essentially Vista SP3)
      Windows 8.x - good with Classic Shell
      Windows 10 - sucks

    19. Re: So much for "one Windows"... by TheFakeTimCook · · Score: 1

      Yup, beginning to look like Apple and Android, along with Linux. All oses make you run their specific type of program. So what's so bad about win10? Keyloggers? On all three. Ads? On all three, specific updates sameo, the difference is, that win supports legacy hardware, the only one different, is Linux. They do the same, support legacy, Apple and Android have definite drop dead dates. No longer support. I may have to look at arm to get support for my four year old tablet, cool.

      Excuse me, unlike Windows 10, Spyware Edition, there are no general-purpose "keyloggers" in macOS or iOS.

      You can also "opt-out" of Spotlight searches being sent out for deeper searching, and prevent certain anonymized iTunes library and usage info from being sent out (and that's not a keylogger). And after those two are defeated by their readily-accessible and clearly-marked GUI "switches", I don't believe there are any other "keyloggers" at the OS-level in those two OSes.

      There are absolutely no "ads" at the OS-level on macOS or iOS.

      I would imagine that TVOS and watchOS are the same on both points; but I don't have any personal experience with them.

    20. Re:So much for "one Windows"... by Anonymous Coward · · Score: 0

      2K wasn't a consumer level OS.

      The statement was about "odd numbered Windows" not "odd numbered consumer Windows".

      But of course it wasn't. I could perhaps even claim that that's what made it good.

  2. Is this it? by jezwel · · Score: 1

    So, W10ARM runs on ARM and runs ARM and Win32 apps from anywhere; mobile devices have a dock for large screen, kb & mouse; and ARM devices are pretty much mobile phones and tablets.
    Is this the converged device businesses have been looking for?
    I'm in software licence management, so converging devices can simplify management effort considerably...

    1. Re:Is this it? by ArmoredDragon · · Score: 1

      I'd say only if it runs native ARM apps and has an unlockable bootloader so you can install third party security software.

    2. Re:Is this it? by ArmoredDragon · · Score: 1

      Er rather, not apps, but native Win32 ARM applications that come in PE binaries.

    3. Re:Is this it? by Anonymous Coward · · Score: 1

      This is a mistake.

      Allowing x86 apps to run on ARM means you get all the x86 malware. Whatever software emualation is invoked is also going to be WORSE than the PPC to x86 rosetta that Apple had. Rosetta basically ran PPC software at 25% the performance of cross-compiled software. x86 to ARM is likely on the factor of 12. ARM to x86 is already about 8-12X slower.

      Like, the smart thing would be for x86-64 hardware to have an FPGA core that can be reprogrammed as ARM or reprogrammed as h.264/h.265/whatever other codec/compression shit comes out.

    4. Re:Is this it? by Anonymous Coward · · Score: 0

      Wut.

      ARM devices are for low power consumption in portable devices. Slapping an x86 and an FPGA into one kinda defeats the point. And if you're on a desktop, just use x86 apps...

      Not to mention the cost of integrating an FPGA into a motherboard

    5. Re:Is this it? by Anonymous Coward · · Score: 0

      This is a mistake.

      Allowing x86 apps to run on ARM means you get all the x86 malware.

      Sure, but they aren't running natively.
      Even if the emulated environment have access to the system files they are for a different architecture so unless the malware is specifically written to handle this it will be stuck in the emulated environment.
      The big question is how separated different x86 programs will be. Will a program infected with malware be a able to spread to other x86 programs?

    6. Re:Is this it? by K.+S.+Kyosuke · · Score: 3, Interesting

      Whatever software emualation is invoked is also going to be WORSE than the PPC to x86 rosetta that Apple had.

      ...why? Because dynamic translation technology is getting worse in time? Unlike compilers in general? For what reason would that be?

      --
      Ezekiel 23:20
    7. Re:Is this it? by Megane · · Score: 1

      Not to mention that the whole point of emulating apps for the same OS with a different instruction set is that most of the time is taken up inside the OS and its libraries anyhow. If 5% of your time is spent running at 25% of the speed, you don't lose much.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    8. Re:Is this it? by c · · Score: 2

      ...why? Because dynamic translation technology is getting worse in time?

      I'd imagine it's got to do more with the relative performance difference between the two architectures. x86 emulating PPC worked because the x86's they were shipping were more powerful than the PPC's they replaced. Ditto for the PPC's emulating 68k. x86 emulates ARM without breaking a sweat.

      ARM trying to handle the x86 instruction set... yes, it can be done, but whether it can be done well or run enough of the Windows application ecosystem to be worthwhile/marketable is questionable.

      --
      Log in or piss off.
    9. Re:Is this it? by Anonymous Coward · · Score: 0

      Because APPLE IS THE BEST!!!!!!!1111 Micro$oft Wangblows is teh suxx0r.

    10. Re:Is this it? by K.+S.+Kyosuke · · Score: 1
      The x86s were not massively faster than the PPCs. They were somewhat faster.

      ARM trying to handle the x86 instruction set... yes, it can be done, but whether it can be done well or run enough of the Windows application ecosystem to be worthwhile/marketable is questionable.

      It doesn't matter for a lot of legacy applications of interest. They used to be run at much slower PCs anyway.

      --
      Ezekiel 23:20
    11. Re: Is this it? by Anonymous Coward · · Score: 0

      No, probably not. It will run x86 win32 apps under CPU emulation but I have not seen any news about native win32 ARM support. Win8 ARM would only run win32 ARM apps if you hack it with a remote debugger.

    12. Re: Is this it? by Anonymous Coward · · Score: 0

      It's the same as 32 bit apps on 64 bit Windows (WoW64) today except that ntdll.dll calls into a emulation layer instead of switching the CPU to 64 bit when calling the kernel.

  3. 1 step forward, 2 steps back by marcle · · Score: 3, Insightful

    Advances in interoperability, but still a horror show in privacy or autonomy.

    1. Re:1 step forward, 2 steps back by Anonymous Coward · · Score: 0

      True, but at least this might lure laptop vendors to try making ARM laptops. Many of us could not care less for Win10, but this might finally get us running Linux on ARM.

    2. Re: 1 step forward, 2 steps back by Anonymous Coward · · Score: 0

      Yea right. MS will no doubt force laptops vendors to lock ARM UEFI to 'on' for any laptop capable of running Win10 ARM.

      This is a short-term ploy to try out the ARM market again... once it catches on they'll then make the Windows Store mandatory on BOTH x86 and ARM. Don't fall for it people.

  4. Wow, Deja-Fu. by roc97007 · · Score: 1, Insightful

    ...that's like Deja-Vu, but what you're remembering was getting kicked in the head some time ago.

    ...I remember an IBM salescreature, telling me sometime in the nineties about an upcoming operating system that would run AIX or MacOS binaries, interchangably, on either the RS6000 or Mac platform. And they weren't even talking (at the time) about running on different architectures.

    On the other hand, virtualization has made giant strides since then, and Microsoft has needed for some time a viable presence in the ARM arena. There was WinCE, (pronounced "wince") and Surface RT, (motto: good luck finding apps) and now there's Win10 Arm (or whatever they're calling it). Hopefully it'll be more successful than the first two. But I can't read "it'll run this, it'll run that, it'll run everything! isn't that exciting!" without thinking of that IBM guy all those years ago.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    1. Re:Wow, Deja-Fu. by DaHat · · Score: 1

      I remember those sales pitches too, though they weren't talking virtualization, only a common hardware platform to rule/replace them all which each os had to target and bring full support for: https://en.wikipedia.org/wiki/...

      This new world of virtualization all the things is certainly going to create some fun debugging problems in the future, assuming anyone cares to run multiple levels on top of each other in another decade.

    2. Re:Wow, Deja-Fu. by roc97007 · · Score: 1

      I think it's already happening. There's already people running apps in a sandbox inside a virtual container that's running inside another sandbox running on a vmware server instance. They're talking about an app that'll magically set all of that up. I wonder if we'll see bugs that cause infinite recursion, like two mirrors reflecting each other.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    3. Re:Wow, Deja-Fu. by Anonymous Coward · · Score: 0

      I think it IBM's Z-marchine. They designed it to support custom instruction sets and could run multiple OS's concurrently, each with it's own memory layout.

      https://en.wikipedia.org/wiki/Z/Architecture

      some CPU's did allow custom downloadable microcode, so that programmers could add their own extended instruction sets.

    4. Re:Wow, Deja-Fu. by swb · · Score: 1

      I had a conversation just the other day with someone who has managed to automate deployment of an entire VMware cluster as nested virtual machines on VMware.

      We've considered nested virtualization at work for both production and proof of concept and demonstration where the actual physical hardware is irrelevant or where we'd prefer to keep the top level hardware/virtualization config in a given state for other purposes.

      As an experiment, I built a 4 node vSAN cluster as a single VM (nested virtualization). It was too small to do anything practical, but I kept it anyway as it was a fairly portable way to preserve a time-consuming setup.

      My gut instinct is that virtualization above a single level of nesting has some performance issues that haven't been addressed, but it may be simply because the hardware capable of meaningful nesting hasn't been widely available (terabyte scale RAM, 10+ GB networking, all flash storage, many cores).

    5. Re:Wow, Deja-Fu. by Anonymous Coward · · Score: 0

      Alternatively, deja moo: the feeling that you've smelled this bullshit before.

    6. Re:Wow, Deja-Fu. by Megane · · Score: 1

      Nope, it's like the guy in the other sub-thread was saying, it was CHRP (basically a common BIOS and architecture for all PPC systems) and one of Apple's many attempts at a new OS (either PowerOpen or Pink). PowerPC was going to be the one thing to rule them all.

      Then something happened. IBM decided to only make high-powered server CPUs, and Motorola decided to only make low-powered embedded CPUs. Apple was stuck in the middle with no CPUs that they could use for laptops (weak FSB) and no CPUs that they could use for desktops without using liquid cooling (don't buy a used G5 tower, it might leak!). So Steve Jobs said fuck it, we're going with five blad... er, Intel.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
  5. MacOS redux by mnmn · · Score: 2

    Reminds me of MacOS emulation for powerpc/m68k. Sounds good in theory but becomes extremely slow in practice.

    This is not just emulating API calls like Wine or containing supervisor mode like most virtualization systems, this is machine language translation on the fly (mame).

    Binary translation has always been slow and unreliable, with the sole exception of arcade games in mame.

    Now if they were trying to emulate ARM on Intel, that would be much more interesting, especially if Intel got involved and provided microcode to directly run ARM machine code..... can't do that in ARM.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
    1. Re:MacOS redux by imgod2u · · Score: 1

      I would imagine the vast majority of software downloaded for Win32 isn't very demanding performance wise. The only major exception to that statement I can think of is Chrome. Which probably won't offer a Windows universal app and also be very resource intensive.

      Then again, Microsoft is actively trying to push people away from Chrome and onto Edge so from their perspective, it's a non-issue.

      Professional apps that are performance intensive but not ported to ARM usually have very regular and non-exotic instruction sequences, so translation wouldn't be very hard for those.

    2. Re:MacOS redux by unixisc · · Score: 1

      Reminds me of MacOS emulation for powerpc/m68k. Sounds good in theory but becomes extremely slow in practice. This is not just emulating API calls like Wine or containing supervisor mode like most virtualization systems, this is machine language translation on the fly (mame). Binary translation has always been slow and unreliable, with the sole exception of arcade games in mame. Now if they were trying to emulate ARM on Intel, that would be much more interesting, especially if Intel got involved and provided microcode to directly run ARM machine code..... can't do that in ARM.

      MacOS emulation was a temporary solution, while Apple's engineers continued porting as much of the OS as possible to PowerPC. It was never something meant to last forever. And once OS-X was out (before the 'next' (pun intended) migration to x86), PowerMacs had their completely native OS.

      That's different from this saga. We had Windows RT, which ran only native apps. Unfortunately, Microsoft never allowed developers to make apps available for this platform outside their Windows Store, which was why it bombed. Now, they're going the emulation route. Emulation is always an interim solution, never a long term one.

      The best example of how emulation works w/ Windows can be seen w/ Windows NT on RISC, such as the Alpha or the MIPS. DEC had fx!32, which was supposed to emulate and dynamically translate software, making things faster every time they were run. But emulation just sapped the legendary performance of the Alpha. Had Microsoft seriously supported Windows NT on RISC in the 90s, they'd have had not just an OS as portable as Linux or NetBSD, but also a 64 bit OS long before x64 came along.

      Also, given the death of the Lumia line of phones, I don't get the point. I have Windows 10 Mobile on my Lumia 550, and it has more native apps than Windows 10 from the Windows Store (not counting legacy win32 or even Windows 7 type win64 apps). Apps like Yelp!, Fandango, Groupme, et al. Yet Microsoft has stopped promoting phones in their store, other than the HP Elite. So what's the point in bringing in a capability to a line that they've discontinued?

    3. Re:MacOS redux by unixisc · · Score: 1

      The 90s called. DEC would like a word w/ you re: Windows NT running win32 applications on the Alpha

    4. Re:MacOS redux by xvan · · Score: 1

      The price difference for low end devices is huge between ARM and Intel. The cheapest android tablet is less than half the price the cheapest windows tablet.

    5. Re:MacOS redux by drinkypoo · · Score: 1

      Now if they were trying to emulate ARM on Intel, that would be much more interesting, especially if Intel got involved and provided microcode to directly run ARM machine code..... can't do that in ARM.

      Seems to me like what's really wanted here is a system with both x86 and ARM processors in the same box, whether they're on the same chip or not. I can imagine power saving advantages to either approach, and don't really know which would actually be lower-power (x86 and ARM in the same CPU package, or not.) The ARM stuff should be a cost afterthought compared to x86, especially if it's integrated either into the CPU or into the NB.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    6. Re:MacOS redux by squiggleslash · · Score: 1

      Almost all games are Win32. Unsure why, I'd have expected them to benefit most of all from more efficient 64 bit instructions, and the latest games aren't generally written to run on older platforms, but 32 bit they generally are.

      Oddly enough,the one example of a Win32 application you gave, Chrome, is being phased out on ix86-32 (might already be, for all I know...)

      --
      You are not alone. This is not normal. None of this is normal.
    7. Re:MacOS redux by jonwil · · Score: 2

      Clearly you are not a video gamer if you think the "vast majority" of win32 software isn't demanding performance wise.
      Good luck writing a translation later, emulator, dynamic recompiler or other technology that can run, say, Fallout 4 on a W10ARM device. Or even something older or less resource demanding like Red Alert 3.

    8. Re: MacOS redux by Anonymous Coward · · Score: 0

      This isn't for games, it's for line of business applications, the vast majority of which aren't very resource intensive.

    9. Re:MacOS redux by Anonymous Coward · · Score: 0

      Not the same thing by any means... Win NT for Alpha didn't run x86 binaries.. same code base, but everything had to be recompiled for the Alpha version...

      Win NT for Alpha was more like how google runs android on ARM and x86 than this Microsoft solution..

    10. Re:MacOS redux by Anonymous Coward · · Score: 0

      Sigh.. there is no such thing as win64... you are confusing the win32 is an api which supports the intel/amd 64 bit instructions

      There is no such thing as the win64 api...

    11. Re:MacOS redux by gwolf · · Score: 1

      Reminds me of MacOS emulation for powerpc/m68k. Sounds good in theory but becomes extremely slow in practice.

      This is not just emulating API calls like Wine or containing supervisor mode like most virtualization systems, this is machine language translation on the fly (mame).

      Worse than slow. At least, the reason to migrate from m68k to Power was better performance, and a cleaner architecture for the future of the platform. And while ARM is much cleaner than Intel... The fastest ARMs now are way slower than their x86 counterparts — And that won't change, because they were _designed_ to be so. ARM is a clean-RISC architecture, oriented to low electrical consumption (and low heat dissipation). Not intended to be a match performance-wise for x86 behemoths.

    12. Re:MacOS redux by caseih · · Score: 1

      Think you're confused about the "win32" moniker. When people say "win32" that's shorthand for traditional Windows apps, using the traditional Win32 API, be they 64-bit or 32-bit, written in C++, compiled to a PE executable. The term has nothing to do with being only 32-bit. There is no Win64. It's just Win32, and there are 32-bit and 64-bit flavors. I'm sure many games probably are full 64-bit now.

      Chrome is now 64-bit only, but it's a traditional app built on the Win32 api.

      I'm not sure if this emulation layer will emulate just the 32-bit version of Win32, or if it will also do 64-bit emulation.

    13. Re: MacOS redux by Anonymous Coward · · Score: 0

      Nope it could run unmodified x86 executables

    14. Re: MacOS redux by unixisc · · Score: 1

      Right - under fx!32

    15. Re:MacOS redux by unixisc · · Score: 1

      That's b'cos the typical x64 configuration has several times more memory, CPU, storage than the typical ARM configuration.

    16. Re: MacOS redux by hvdh · · Score: 1

      I'm currently analyzing some data using Excel. Not too big, 3 sheets with 12k rows each, and some simple formulas containing lookups. Whenever i change the input date, Excel is re-calculating things using all 8 cores of my Core i7 desktop CPU for about 30s.

    17. Re:MacOS redux by Anonymous Coward · · Score: 0

      Much like you can't run x86 Linux binaries on a Raspberry Pi. All MS did was port the OS to a new architecture. You could even get NT on IBM PPC boxen.

    18. Re: MacOS redux by Anonymous Coward · · Score: 0

      That had nothing to do with the architecture of your CPU and everything to do with the fact that you are using a spreadsheet when you ought to be using a database.

    19. Re: MacOS redux by Anonymous Coward · · Score: 0

      Dont use Excel: people use excel because it starts out easy and it is what they got, but as the task grows in complexity and data you hit a barrier both performance wife, but also conceptually in that the code is stored along with the data in a binary file, making it impossible to use common sense software practices such as revision control.

    20. Re:MacOS redux by Anonymous Coward · · Score: 0

      They would have to be on the same chip in order to implement cache snooping given the potential to be reading and writing the same memory.

    21. Re: MacOS redux by Cesare+Ferrari · · Score: 1

      Nonsense. Excel is an excellent tool when used for it's main purpose, which is as a spreadsheet (obviously). The moment you start hacking VB into it, and connecting to remote data sources, you're way off the sensible path. As a viewer on ad-hoc generated reports from things like accounting packages, it's great, and that's what businesses tend to do with it these days.

      If I were to complain about excel, it would be some of the daft csv import logic which means that dates and times aren't parsed in a sensible manner, and the most ludicrous restriction meaning you can't open two docs with the same name (can't believe this is still an issue).

    22. Re:MacOS redux by qaz123 · · Score: 1

      They can translate it once, then reuse the result. How is it different than compiling from other languages or bytecodes? You take the program written in the language that is not understood by the processor and translate it to the language that is understood by the processor. (Of course I understand that not all software can be translated like that)

    23. Re:MacOS redux by sad_ · · Score: 1

      Seems to me like what's really wanted here is a system with both x86 and ARM processors in the same box

      I think Apple is working towards this, their main OS will be iOS and the x86 CPU will be something similar to a 'high performance' CPU in the system you can offload certain tasks to, much like you can do now with your GPU.

      --
      On a long enough timeline, the survival rate for everyone drops to zero.
    24. Re:MacOS redux by TheRaven64 · · Score: 1
      Modern binary translation is very fast. MAMBO, for example, translates AArch32 to AArch64 and performs better than native on the same chip. The main problem is that it consumes extra RAM. The approach taken by Transitive Technologies (which Apple licensed and branded as Rosetta) involves generating small trampolines to allow calling native code. Rosetta's emulation wasn't very good in comparison to the state of the art, but it didn't matter because most desktop apps spend 50-90% of their CPU time in system libraries and these were all native code.

      Now if they were trying to emulate ARM on Intel, that would be much more interesting, especially if Intel got involved and provided microcode to directly run ARM machine code..... can't do that in ARM.

      In general, it's easier to emulate a more CISCy ISA on a more RISCy one, so they're doing it exactly the right way around.

      --
      I am TheRaven on Soylent News
    25. Re:MacOS redux by Anonymous Coward · · Score: 0

      I could comfortably fit a 32-bit Linux development distro with all C++ librarie and utilities in 20 Gigabytes. Going up to 64-bit, the disk space required goes up to 60 Megabytes. Just because the instructions have doubled or tripled in size.

    26. Re:MacOS redux by Anonymous Coward · · Score: 0

      Modern arm is no arm7tdmi. Unfortunately.

    27. Re:MacOS redux by Megane · · Score: 1

      The reason the original PowerPC transition had such bad performance was that 7.5.x (and I think 8.x as well) still had most of the OS written in 68K code. Microsoft has been doing the ARM thing long enough that they don't have legacy binaries to deal with.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    28. Re:MacOS redux by bluefoxlucid · · Score: 1

      The Common Intermediate Language is an ISA. For certain common operations, CIL is faster than C++; for others, it's been variable across runtime versions. Linked list and array iterations are one area that gets batted back and forth, with various implementations shown faster in C++ or in C#. Some problems are just faster to solve in C# than C++ because the runtime profiling in the CLR constantly adjusts the expected likely branch in a loop or whatnot, and so it keeps tweaking itself to run as fast as possible at the current moment while running through large data sets.

      LLVM will take x86 or ARM code, convert it into an internal static single assignment tree, and run compiler optimizations. It'll then spit out x86-64 code, ARM code, m68k code, or whatnot. It's not like you can't do this stuff with real-world ISAs instead of specially-designed software ISAs.

    29. Re:MacOS redux by bluefoxlucid · · Score: 1

      I'm amazed to learn that 105,840 is three times 104,508:

      $ ls -l|awk '/^-/{print $1,$5,$9}'
      -rw-rw-rw- 2233770 coreutils_8.13-3ubuntu3.3_amd64.deb
      -rw-rw-rw- 2193296 coreutils_8.13-3ubuntu3.3_i386.deb
      $ ls -l */bin/ls|awk '/^-/{print $1,$5,$9}'
      -rwxr-xr-x 105840 amd64/bin/ls
      -rwxr-xr-x 104508 i386/bin/ls
      $ du -sh i386/ amd64/
      8.0M i386/
      8.3M amd64/
      $ du -sh i386/bin amd64/bin
      2.5M i386/bin
      2.8M amd64/bin

    30. Re:MacOS redux by bluefoxlucid · · Score: 1

      How do multi-chip x86 machines do it, then?

    31. Re: MacOS redux by Anonymous Coward · · Score: 0

      Lol, keep thinking ARM will emulate x86 acceptably for nontrivial programs.

    32. Re:MacOS redux by Jeremi · · Score: 1

      Binary translation has always been slow and unreliable, with the sole exception of arcade games in mame.

      Hmm, I always thought Apple's Rosetta (PowerPC->x86) translator did a very good job. I'm not sure what their secret sauce was -- maybe it was just that Intel chips at the time were sufficiently faster than PowerPC chips that any program that ran well on PowerPC would also run well on a faster Intel chip, even with the translation overhead.

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
    33. Re:MacOS redux by ray-auch · · Score: 1

      The best example of how emulation works w/ Windows can be seen w/ Windows NT on RISC, such as the Alpha or the MIPS. DEC had fx!32, which was supposed to emulate and dynamically translate software, making things faster every time they were run. But emulation just sapped the legendary performance of the Alpha. Had Microsoft seriously supported Windows NT on RISC in the 90s, they'd have had not just an OS as portable as Linux or NetBSD, but also a 64 bit OS long before x64 came along.

      fx!32 didn't just dynamically translate, it also cached bits of native code translations for subsequent runs. We had some alphas on demo at the time and they were beautiful machines, didn't notice much, if any, performance hit from fx!32 - in fact I think we stopped bothering to recompile our applications and just ran the x86 versions because there was no benefit in it.

      The real problem was that Alpha (sadly) failed as a platform. The issue has never been that MS doesn't have a portable OS, the issue has always been that they are on by far the most popular hardware platform already, releasing and supporting a port costs (big) money and for what? The landscape is now changed, Intel have ditched their low power ARM competitor (Atom), so ARM is now king in low power with no other contenders, there is incentive to port.

      In fact if you look at the previous attempt (windows RT) and compare with Intel releases, it looks a lot like Windows RT's purpose was to kick Intel into delivering better performance on Atom (they did, and RT promptly got shelved).

    34. Re:MacOS redux by Anonymous Coward · · Score: 0

      Those processors have some extra logic, called the QPI interface (QuickPath Interconnect). One processor sends a snoop broadcast to the others with the changes that have occurred. The other processor then update their state accordingly. The problem is speed, with a L1 cache, that's only 4 clock cycles, with a remote memory transfer, that's 300 clock cycles. Getting close to the performance difference between a GPU solution and CPU one.

      http://frankdenneman.nl/2016/07/11/numa-deep-dive-part-3-cache-coherency/

    35. Re:MacOS redux by angel'o'sphere · · Score: 1

      I had around 2004 a 17" PowerBook, running Mac OS X 10.4 (Panther).
      I played Diablo on it, not sure if it was Diablo II, that was an 68k game running under Rosetta.
      I did not notice any performance problems.

      --
      Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
    36. Re:MacOS redux by Shirley+Marquez · · Score: 1

      Chrome on x86 is not yet 64 bit only, and won't be for some time - there are still too many machines running the 32 bit version of Windows. What changed recently is that they automatically install the 64 bit version on compatible systems, rather than people specifically having to download it, and have also started to offer to upgrade installations of 32-bit Chrome to the 64 bit version. It probably won't be long until they REQUIRE the upgrade to 64 bit on 64 bit Windows and only allow you to run the 32 bit version on 32 bit Windows. Google will eventually drop support of 32 bit Windows but it's probably a couple of years away.

      Chrome on macOS and Linux is 64 bit only. That does mean that the small number of people still running 32 bit versions of those OSes can't run current versions of Chrome. On the Mac that only applies to ancient versions of macOS that are no longer supported anyway. But many current Linux distributions still offer 32 bit versions because lots of Linux users run legacy hardware; part of the appeal of Linux is that you can run current versions on hardware that is no longer supported by other OSes. Chrome won't work on those, though its open source relative, Chromium, can still be built for 32 bit Linux for now.

    37. Re: MacOS redux by imgod2u · · Score: 1

      Luckily, Excel is available as a Universal Windows App...

  6. Only LUDDITES use LUDDITE x86 apps! by Anonymous Coward · · Score: 0

    Modern app appers only app APP apps, NOT LUDDITE x86 apps!

    Apps!

    1. Re:Only LUDDITES use LUDDITE x86 apps! by Anonymous Coward · · Score: 0

      Can I jam my dick in your ASS?

    2. Re: Only LUDDITES use LUDDITE x86 apps! by Anonymous Coward · · Score: 0

      Donald?

    3. Re: Only LUDDITES use LUDDITE x86 apps! by Anonymous Coward · · Score: 0

      Donald is neither gay nor a n1gger, so he surely can't be a member of Gay N1gger Association of America.

    4. Re:Only LUDDITES use LUDDITE x86 apps! by Big+Hairy+Ian · · Score: 1

      Actually I just don't want to be constrained by what they say I can have from the App Store

      --

      Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.

  7. Better than nothing by Anonymous Coward · · Score: 0

    Seriously it's better than nothing. And at least it can make calls to native libraries.

  8. Left Hand, by Anonymous Coward · · Score: 0

    I'd like to introduce you to the Right Hand. You'll be separated again once our ARMs are ready to serve the market.

  9. Just like OSX then by GreatDrok · · Score: 1

    Having been through the OSX transition from PPC to x86 this sounds very much like they've bought in Transitive's technology to allow them to dynamically recompile x86 native applications (I refuse to call them 'apps') to run on ARM. Apple handled this pretty well and there was very little that didn't work. We lost MacOS9 support, but we gained performance for native applications and PPC binaries actually ran surprisingly well if they were mostly GUI based. I did compile a few command line tools and run them under Rosetta and they were about 10x slower than native (still impressive honestly) but for something like MS Word the hit was much less. Today I can still run Word 2004 on my x86 MacBook under VMware which allows me to run Snow Leopard and it runs faster than the native Word 2016 I have on macOS Sierra. Go figure. Anyway, this is something MS should have done from the start as the technology was already out there but I suspect politically they wanted to push the store apps (yeah, those are apps) rather than let people continue running their old x86 binaries. That worked well for them didn't it?......

    --
    "I have the attention span of a strobe lit goldfish, please get to the point quickly!"
  10. The best way to break Windows... by Anonymous Coward · · Score: 0

    ...is to punch an ARM through.

  11. Microsoft for once get one good job by n329619 · · Score: 1

    I give you half a clap, for being too late at adding this in Windows RT and basically everything Microsoft did to chase Google/Apple in the mobile ecosystem.

    Part of the reason Windows 7 became the successor to windows xp and windows vista is the "xp mode". A VM designed to be well integrated lay for previous software compatibility.

    This ARM emulator layer might not be prefect or even fully feasible, but it should be good enough to actually put consumers on ARM windows. It will also retain some windows developers from leaving windows as the market shift to mobile. Not that I encourage any of that because Microsoft been a d**k pushing people to Windows 10.

    Unfortunately at the current stage, it's only making windows on mobile semi-relevant as a lot of consumers and developers have already left windows.

    1. Re: Microsoft for once get one good job by Anonymous Coward · · Score: 0

      You hit the nail on the head about Windows XP Mode on Windows 7. We encountered client after client with legacy applications that wouldn't run on Windows 7 but XP Mode allowed them to move to Windows 7 without also forcing them to upgrade their line of business applications. As as a result we could move many clients to Windows 7 machines as their XP systems died and still make things work until they moved to new software. It was great for bridging that gap.

    2. Re: Microsoft for once get one good job by unixisc · · Score: 1

      Too bad Microsoft didn't see it worthwhile to include a Windows 7 mode under VirtualPC and then make it available to Windows 8 & 10 users. Had they done that, there'd have been a lot less howls in the industry over the upgrades. In fact, Microsoft could make good money selling something like VirtualPC w/ support for every legacy Microsoft OS - from Windows 95 to Windows 7, and make sure it runs on Windows 8, 10 and Server.

    3. Re: Microsoft for once get one good job by Anonymous Coward · · Score: 0

      Any serious business would ensure continuation of support for their software. Your clients are probably trashy 3rd party vendors. Anyway.

      Most people just go web these days, with the advent of single-page web applications and whatnot. Nobody cares anymore, as long as your browser can handle it.

  12. MS Conceding - Everyone Wants x86 Apps by Anonymous Coward · · Score: 0

    With this, they're pretty much conceding that the only reason people use Windows is because they want to use Win32/64 applications, and because they have no choice. They have the lock on the x86/x86-64 market, so they can afford to start forcing people into their walled garden, or at least try to do so. No one wanted Windows Phone, so they can forcefully bring Windows Phone to these customers, largely whether they like it or not. However, in ARM space they have Android to contend with, which is far more powerful than they are on the platform. As such they're trying to take the most desired feature, despite architectural incompatibility, and use it to lure in users while they to try to make a stand against Android. Arguably they're also conceding that everyone hates the "no Win32" idea for Windows S 10. They know people hate the things they have in mind, and don't care, so long as they can use their monopoly to try to force people into doing what they want. It seems that Microsoft is truly determined to make up for lost time since the antitrust ruling, and then some.

    Here's hoping they'll fuck it up. I don't want to have the Microsoft nanny deciding what I can and can't do with my computer and data, and the Win10 push for the cloud is trying to hand over just that to them, with hardware that I paid for, but in practice, they control. And yes, I know, Linux, but I'm not holding my breath that they won't make at least an attempt to prevent it or any other alternative OS that they don't control from being installed on x86 hardware sooner or later. Given the problems UEFI's Secure Boot has caused, and the changes to its requirements that came with Windows 10, arguably it's already well on its way there.

  13. Almost A Decade Too Late by Anonymous Coward · · Score: 0

    This would've been a smart move 9 years ago when smart phones were first becoming mainstream. The devs who make the best mobile software are committed to iOS and Andriod. Had Microsoft shipped a version of Windows that ran on ARM processors that could also run x86 software Microsoft could've won the mobile war. It's too little too late at this point. Devs interested in offering mobile apps long ago committed to native iOS and/or Android based applications and aren't coming back to an ARM based Windows platform anytime soon. That ship has sailed.

  14. The albatross has been removed from their neck by Anonymous Coward · · Score: 0

    The Windows store is a freaking shiatshow and MS loves to obsolete devices tied to that store. With x86 compatibility and no store lock-in I'm keen to give this a trial run when I buy my next tablet. No doubt x86 multimedia codecs will run like crap on this device but eventually that won't matter as much.

  15. Jeeze by Anonymous Coward · · Score: 0

    It is articles like these that keep me away from Slashdot commenting. The arrogance and the elitism is far too much for me to handle.. have fun jerking each other

  16. Dynamic code generation? by K.+S.+Kyosuke · · Score: 1

    I'm wondering how software with in-process code generation (such as LuaJIT, Smalltalk VMs, Lisps etc.) is going to fare.

    --
    Ezekiel 23:20
  17. Finally catching up with Apple by Anonymous Coward · · Score: 0

    Because this sort of technology was around in Apple Macintoshes TWICE. And ofc they emulated a whole OS too!

    Apple had this during the 68k>PPC transition, and reintroduced it during the PPC>intel transition. And if you bought a PPC Mac running OS X, you could even virtualise Mac OS 9 to run all your classic apps.

    Well dome Microsoft, for catching up!

    1. Re:Finally catching up with Apple by ray-auch · · Score: 1

      Um, you know MS had exactly this sort of technology on Windows back in the early 90s right? When Windows NT ran on DEC Alphas as well?

      MS arguably did it better - they didn't need to emulate the OS because they could recompile it for Alpha (as they do now for ARM). Win NT has always been a portable OS. Apple only had to emulate OS level stuff because they wrote hardware-specific stuff into the OS in the first place.

  18. Got to start somewhere by mccalli · · Score: 4, Insightful

    This is a good thing. Like the 68k->PowerPC, and then the PowerPC->Intel transition - you've got to start somewhere, or you're stuck on one architecture forever.

    I see the negativity in many of the posts. I don't understand it. You have to make a start somehow, and this is a good one. If you then allow cross compilation in Visual Studio, then you're essentially taking the same approach Apple did to manage its transitions, and those transitions were damned near seamless. Thanks Microsoft for trying to move and do something different. And yes, I really mean that.

    1. Re:Got to start somewhere by Anonymous Coward · · Score: 0

      The only reason they're doing this is because Win32 compatibility is one of the few actual selling points of Windows. The other main one, lack of choice, is already there for x86, which is why they're pulling what they are in Windows S 10, so they can use the Windows Store to control all the software you can use on it, and help to control Win10 computers in general. On ARM, they have to compete with Android, hence bringing one of the few things about it everyone still likes, whereas where their competition is much more limited and people have little choice (x86), they're stripping it out to serve their purposes. If they succeed and cripple or destroy Android, they'll finish off Win32 outright and swap to Windows S 10 - ARM Edition.

      My only question is when they'll start pushing this into Windows 10 Pro. My guess is sooner than anyone expects.

    2. Re:Got to start somewhere by jimbob6 · · Score: 1

      Yea soon we will be able to get rid of this old ARM crap and get everything on a propper x86 architecture.

  19. Windows 10 becoming splintered by Anonymous Coward · · Score: 1

    Microsoft seems determined to splinter Windows into multiple versions with variable types of app support. Its going to seriously confuse the average user. I do not know what choice many will have to move beyond Windows, but I am certain this is a opportunity for other operating systems to take advantage. At this point, if I am going to be locked into a wall garden I think I will choose Apple or Google over Microsoft.

  20. Why oh why? by Anonymous Coward · · Score: 0

    Explain to me who uses windoze 10 in ARM and why? I'm too lazy to googl and i really dont care.

  21. Backward Compatibility is a Boon by pubwvj · · Score: 1

    I wish all modern OS's would do this. There is a lot of legacy software out there that we still need and far more that would just be nice to have access to such as children's educational software that was never remade for the new OSs. Right now a lot of businesses, and families, end up having to maintain old computers to access that older software, some of which is mission critical. The modern hardware has plenty of computing power to do the emulation and modern security methods means it can be sandboxed to run safely.

    I hope to see both Microsoft and Apple offering legacy support and even crossover support.

    1. Re:Backward Compatibility is a Boon by Khashishi · · Score: 1

      Backwards compatibility for software is easy. Backwards compatibility for hardware is not so easy. Often, we have to maintain old computers to access old hardware.

    2. Re:Backward Compatibility is a Boon by pubwvj · · Score: 1

      Correct. And having the new OS's support legacy software would solve more than half the problem. In my experience the legacy software problem is larger than the legacy hardware problem. It would be great to have both but as you point out, the software end is easier. There is no good excuse for Apple and Microsoft creating this problem.

  22. Good. Intel needs the competition by Khashishi · · Score: 1

    and Chromebooks aren't quite giving it.

  23. Support for non-store native ARM applications? by Anonymous Coward · · Score: 0

    The article doesn't say.

  24. More Spying Potential by Anonymous Coward · · Score: 0

    MS just realized they were missing out on whole market segments.

    This move gives them the ability to truly corner the market on consumer spying.