Daniel Rubino discusses Windows 10X on This Week in Tech
Our executive editor Daniel Rubino discusses Windows 10X on the latest episode of This Week in Tech.
In the latest episode of This Week in Tech, our executive editor Daniel Rubino discusses Windows 10X, dual-screen devices, and Microsoft's approach to a modern Windows. Rubino joined the show's host Leo Laporte as well as Alex Wilhelm and Dan Patterson to discuss Windows 10X and several other topics.
The entire episode is 2 hours and 30 minutes long, so there's plenty of discussion to digest. The discussion about Windows 10X starts around 54:17. Rubino starts off by explaining the basics of Windows 10X, how it's built of Windows Core OS, and summarizing the general thought process behind Microsoft's development of the operating system.
That discussion flows into how Windows 10X gets rid of legacy code while still having the option to run older programs inside containers. Rubino discusses how containers work in the OS and how Windows 10X is lighter than regular Windows 10 because legacy code only runs when you need it to.
After discussing Windows 10X, they move on to how some people managed to get Windows 10X onto unsupported devices, including a MacBook.
- Hands-on with the first Windows 10X developer preview build
- Check out Windows 10X running on a laptop
- Windows 10X will run most, but not all, Win32 programs
- 5 things you need to know about Windows 10X containers, UWP, and Win32 apps
Get the Windows Central Newsletter
All the latest news, reviews, and guides for Windows and Xbox diehards.
Sean Endicott is a tech journalist at Windows Central, specializing in Windows, Microsoft software, AI, and PCs. He's covered major launches, from Windows 10 and 11 to the rise of AI tools like ChatGPT. Sean's journey began with the Lumia 740, leading to strong ties with app developers. Outside writing, he coaches American football, utilizing Microsoft services to manage his team. He studied broadcast journalism at Nottingham Trent University and is active on X @SeanEndicott_ and Threads @sean_endicott_.