The VxD driver does a lot of the heavy lifting and is responsible for initializing WSL9x as well as handling userspace events that have to be relayed to the kernel (i.e., page faults and syscalls), which it does in a rather interesting way due to limitations in the Win9x architecture.
For the longest time, Linux was considered to be geared specifically for developers and computer scientists. Modern distributions are far more general purpose now -- but that doesn't mean there aren't certain distros that are also ideal platforms for developers. What makes a distribution right for developers? Although I consider app compatibility, stability, and flexibility to be essential attributes for most any Linux distribution, developers also need the right tools
I've had several incarnations of the self-hosted home lab for decades. At one point, I had a small server farm of various machines that were either too old to serve as desktops or that people simply no longer wanted. I'd grab those machines, install Linux on them, and use them for various server purposes. Here are two questions you should ask yourself:
I recently wrote about my migration away from VirtualBox to KVM/Virt-Machine for my virtual machine needs. I've found those tools to be far superior (albeit with a bit more of a learning curve) than VirtualBox. Since then, however, I've found another method of working with KVM (the Linux kernel virtual machine technology), one that not only allows me to create and manage virtual machines on my local computer, but also from any machine on my LAN. That tool is Cockpit, which makes managing your Linux machines considerably easier.
Ring the bells, sound the trumpet, the Linux 6.19 kernel has arrived. Linus Torvalds announced that "6.19 is out as expected -- just as the US prepares to come to a complete standstill later today, watching the latest batch of televised commercials." Because while the big news in Linux circles might be a new Linux release, Torvalds recognizes that for many people, the "big news [was] some random sporting event." American football, what can you do?
The updates are installed onto a different (and isolated) system image or subvolume. Once the update finishes successfully, you can switch to the new system by rebooting. Again, if the update isn't 100% successful, it will not happen. And because this all occurs on a separate partition (or image), you don't have to worry about it affecting your system's current state.
The reason for this is Snap - a Linux application packaging format - creates a local Trash folder for each VS Code version, one that's separate from the system-managed Trash, according to a VS Code bug report dating back to November 11, 2024. Not only that, but Snap keeps older versions of VS Code after updates, potentially multiplying the number of local Trash folders and the trashed-but-not-deleted files therein. Emptying the system Trash folder doesn't affect the local instances.
The MSTest framework can be accessed via NuGet. With MSTest 3.4, support for WinUI framework applications is added to MSTest.Runner. With this improvement, a project sample is offered and work is under way to simplify testing of unpackaged WinUI applications. Microsoft also has improved the test runner's performance by using built-in System.Text.Json for .NET rather than Jsonite and by caching command line options.
Open VSX is operated by the Eclipse Foundation, and provides extensions unencumbered by the restriction Microsoft places on the VS Code marketplace that "alternative products including those built on a fork of the Code-OSS Repository, are not permitted to access the Visual Studio Marketplace." Microsoft cites security and compatibility as reasons, and there is no business case to "run a full-scale global service for everyone to use."
