One of the bombshells from CES 2018 was that some Windows PC makers like ASUS, HP, and Acer announced a partnership with Amazon to integrate Alexa with their new products. That's not instead of Cortana, of course, which is built into Windows 10, but it does put arguably the most well known and supported virtual assistant where it has never been before.
So does this mean Cortana should be looking over her shoulder, looking for the proverbial axe? That's what we're talking about in the Windows Central forums.
There's no denying that Alexa is a much more established player in the space. Not only is it supported by Amazon's own hardware, but recent times have seen it expand far beyond that, and now we're going to be seeing it pop up in cars and wearables as well as on PCs, phones and tablets. Anyone who's anyone in the smart home market supports Alexa, and it's available in a number of locations around the globe.
Compare that to Cortana, which until recently was limited to Microsoft's own software platforms before expanding with the Invoke, and now it seems a smart thermostat. Cortana skills are lesser in quantity than Alexa, but most importantly, officially all this extra functionality is limited to the United States.
There's no doubt this latest development is both a good and bad news scenario for Microsoft fans. It's fantastic news that Amazon is bringing Alexa finally to Windows 10, but it does leave concerns over the future for Cortana. But what do you make of it all? Drop by the forums thread below and let us know.
Richard Devine is an Editor at Windows Central. A former Project Manager and long-term tech addict, he joined Mobile Nations in 2011 and has been found on Android Central and iMore as well as Windows Central. Currently you'll find him covering all manner of PC hardware and gaming, and you can follow him on Twitter and Instagram.
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.