2 ms·
> Well, no luck, WinRT's closed policies won't allow that (and it's not a technical issue.). It's true that Microsoft doesn't allow alternative rendering engin
by Amezarak 12y ago
> Well, no luck, WinRT's closed policies won't allow that (and it's not a technical issue.).
It's true that Microsoft doesn't allow alternative rendering engines on WinRT, but it is ARM instead of x86, so there is a technical component; Google would have to port Chrome.
- bentcorner 12y agoThe problem is that only store apps are allowed to be installed on Windows RT devices, and porting Chrome to a store app is not an insignificant amount of work, for what amounts to very little gain (RT customers would be the only ones who benefit). There's an argument that future store-compatible apps are easily ported to WP10, but Google has very little incentive for any of this work. If anything Mozilla had reasons to, but even they killed their efforts due to lack of customer interest.
- Dylan16807 12y agoPort? Android, ChromeOS... Arm is a first-class compile target.
- Amezarak 12y agoYes, in theory. What a blessing it would be if cross-compatibility was always as simple as "recompile with this as the target." That doesn't mean you can take Chromium for Windows and recompile targeting ARM and get something that works on jailbroken WinRT. As best as I can tell nobody has gotten Chromium running, but they have gotten many other x86 applications running. People have already tried. There's more work than that involved.
- Dylan16807 12y agoRight, there's work involved, but it's taking code that already works on ARM, and already works on Win32, and making it work with the ARM version of Win32. Since microsoft disallows that, there's much less incentive to do that work. But it's not an enormous barrier.