- A Qualcomm government has addressed why Chrome isn’t out there on Windows on Arm units.
- The government notes that it’s a “policy problem” reasonably than a technical hurdle.
One of the most effective methods for legacy Windows apps to run quicker on Windows on Arm is for builders to supply an Arm model, permitting the app to run natively on the platform. In the browser area, we’ve seen an Arm port of Firefox in addition to a local model of Microsoft Edge.
Unfortunately, Google hasn’t delivered a local model of its Chrome browser simply yet. Now, Miguel Nunes, senior director of product administration at Qualcomm, has shed gentle on the no-show in a dialogue with journalists.
“The code is done. This is not a technical issue,” Nunes stated in response to a query from Android Authority, noting that the newest iteration of Microsoft Edge makes use of the Chromium engine which powers Chrome.
“The Chrome browser is Chrome engine plus a little bit of things (sic). So it isn’t a technical issue, it’s a policy problem. There’s nothing really preventing them from doing it, just they haven’t done it yet,” Nunes defined. “In fact, we’ve had it all working, it works fine. It’s just (a matter of) them making it publicly available.”
This isn’t the primary time we’ve heard murmurings of a attainable behind-the-scenes concern with Chrome’s launch. Neowin reported final yr that Chrome for Windows on Arm was able to go, however that there was “some kind of disagreement” between Google and both Microsoft or Qualcomm.
Nevertheless, this appears to be the primary time one in all these events has formally acknowledged a “policy problem” being accountable for Chrome not being out there for Windows on Arm. Hopefully it will get resolved quickly, because it’s positively one of many greatest apps yet to obtain an Arm port.