And there's the rub. Microsoft forbids manufacturers of ARM-based Windows devices from allowing customers to disable or customize secure boot.[0] I doubt they'll change that going forward.
>On an ARM system, it is forbidden to enable Custom Mode. Only Standard Mode may be enabled.
[0] https://docs.microsoft.com/en-us/windows-hardware/design/com...
My little 10" ARM chromebook has already left my more powerful laptop gathering dust. It seems like 'just a browser' at first glance, but it becomes so much more when you add a chroot which can launch X sessions into Chrome tabs. These Microsoft ARM machines are encouraging, since they should bring new entries into the ultraportable market, but I think I'll hold off until it's clear that we'll have options with regards to the software.
#20 in https://docs.microsoft.com/en-us/windows-hardware/design/com...
Digital restrictions management lockdowns prevent installing Linux.
Not sure why your first thought is to ride on the back of Microsoft's work...
Sure, you could create a brand new electronics brand and try to market it. But it would be super expensive and take a long time to get off the ground.
So you claim running X sessions in Chrome tabs is better than running X directly?
You could run a WM in a chrome tab, but I prefer breaking out individual programs. Like, I can have KiCAD running in one tab, with the datasheets for parts I'm using in nearby tabs. Or I can just break an IDE out into its own window. It's a small screen, so having the whole browser window dedicated to the program is nice, and you can even use fullscreen mode and navigate with ctrl+[shift+]tab.
ChromeOS has a nice UI. Certainly much nicer than XFCE running in a browser tab.
To me this rather sounds like one should use another window manager than the default one that usual GNU/Linux distributions install if one has a small screen.
I'm no GNU/Linux wizard, but I somehow expect that such a window manager already exists.
In fact, ChromeOs acts as a Window Manager, because it deals with how each application is organized in the screen/ shown to the user; in this setup, no Chrome Apps are used (only programs from chroot are used)
tl;dr: It can be thought as a WM, although it isn't one
- Java
Java applications will not require any recompilations, they will run immediately because they run on a JVM
- C#/VB/F#
Those applications still will run right away because they run in the .NET CLR virtual machine.
- C++, C
These applications, considering they are already using the Windows APIs, should recompile with few changes.
Games, nowadays, are also developed using frameworks. They mostly depend on the GPU nowadays, and the GPU was never x86 architecture either, so no big change there.
Except for the native libraries that they depend on.
http://docs.oracle.com/javase/6/docs/api/java/math/BigIntege...
Seems like a rather poor decision on Microsoft's part. Fortunately rather few things interact with data this way anyways, most serialization formats are text based or include endian information.
I predict that this will have a negligible impact on PC games. They're CPU/memory/GPU bound and will not work well under emulation. They're not likely to get ported. But gamers are not the target market for this product.
Adoption will depend on the killer features, which is currently "LTE" and "uses less power", neither of which PC users care about, so that's why this is doomed to fail.
This doesn't happen on UEFI computers, unless you use the CSM.
ARM SoCs lack the backward compatible x86 BIOS-style bootstrap. This is great because it's kinda crazy to think about booting into stuff like MBR, real mode, etc in 2017. But this is bad because without good standards it's really tricky to have a generic installer for another OS. Also, all or nearly all ARM SoCs have signed bootloaders. Great: less fear of a rootkit/virus hiding in my system. Awful: often used to protect subsidies or other business model hijinks; can't install an alternate OS.