It feels like yesterday but believe it or not; it’s been over six months since Windows 11 was officially launched in the market. To be precise, the operating system came out on October 5, 2021. Compared to Windows 10, Windows 11 is packed with enhanced security features and provides faster access to services you already use, such as Microsoft Teams, Skype, the (new) Edge browser, and more. Most importantly, the OS centers on hybrid work and digital experience to empower remote learning.

When Microsoft rolled out Windows 11 last fall, the announcement included what seemed like a relatively distant deadline: October 14, 2025, the date when Windows 10 support will end. Considering how many unexpected changes we’ve all experienced over the past few years, we understand if you’re hesitant to prepare for anything that’s not scheduled to take place until the year 2025.

We are happy to announce that Bitbucket Pipelines now supports self-hosted runners on Windows. You can create a self-hosted runner and run it on your Windows infrastructure to run builds with the.Net framework. Since you're using your own runner, you won’t be charged for any Bitbucket Pipelines build minutes. This self-hosted runner will be non-containerized, allowing your CI/CD step to access the host’s hardware, such as the graphics card or any connected external devices.

Ubuntu is fast becoming the platform of choice for data scientists worldwide – which is why HP is empowering its customers to launch Ubuntu environments directly on their Windows machines. In addition to native Ubuntu offerings, select Z by HP workstations are also available with Windows Subsystem for Linux 2 (WSL 2) pre-installed and pre-enabled, giving users the ability to accelerate data science workflows on Ubuntu straight out of the box, without leaving their native Windows OS.

OK, first things first. I have to admit that I am, first and foremost, an old-school UNIX systems administrator. I’m that grizzled sysadmin in your shop who soliloquizes wistfully about managing UUCP for email “back in the day.” Centralizing Logs? Yeah, we had syslog, and saved it all off to compressed files.