Microsoft has open-sourced core components of the Windows Subsystem for Linux (WSL), specifically the kernel, drivers, and utilities that make up the user-mode based architecture of WSL itself. This includes the Linux kernel specifically built for WSL, as well as components like the wsl.exe command-line tool. The source code is available under the GPLv2 license on GitHub, allowing community contributions and increased transparency. While this move opens up WSL development, the underlying virtualization technology and Windows integration remain closed-source. This open-sourcing aims to foster collaboration with the Linux community and improve WSL's functionality.
Linux in Excel demonstrates running a basic Linux system within a Microsoft Excel spreadsheet. Leveraging VBA scripting and x86 emulation, the project allows users to interact with a simplified Linux environment, complete with a command line interface, directly within Excel. It emulates a small subset of Linux system calls, enabling basic commands like ls, cat, and file manipulation within the spreadsheet's cells. While highly constrained and not a practical Linux replacement, it serves as a fascinating proof-of-concept, showcasing the flexibility of both VBA and the underlying architecture of Excel.
Hacker News users expressed both amusement and skepticism towards running Linux in Excel. Several commenters questioned the practicality and performance of such a setup, with some suggesting it's more of a novelty than a useful tool. Others were impressed by the technical feat, appreciating the ingenuity and creativity involved. Some discussed the potential for misuse, particularly in bypassing corporate security measures. There was also debate on whether this qualified as truly "running Linux," with some arguing it was merely simulating a limited environment. A few pointed out the historical precedent of running Doom in unexpected places, placing this project in a similar category of playful hacking.
The blog post details the author's process of switching from Linux (Pop!_OS, specifically) to Windows 11. Driven by the desire for a better gaming experience and smoother integration with their workflow involving tools like Adobe Creative Suite and DaVinci Resolve, they opted for a clean Windows installation. The author outlines the steps they took, including backing up essential Linux files, creating a Windows installer USB drive, and installing Windows. They also touch on post-installation tasks like driver installation and setting up their development environment with WSL (Windows Subsystem for Linux) to retain access to Linux tools. Ultimately, the post documents a pragmatic approach to switching operating systems, prioritizing software compatibility and performance for the author's specific needs.
Several commenters on Hacker News express skepticism about the blog post's claim of seamlessly switching from Linux to Windows. Some point out that the author's use case (primarily gaming and web browsing) doesn't necessitate Linux's advantages, making the switch less surprising. Others question the long-term viability of relying on Windows Subsystem for Linux (WSL) for development, citing potential performance issues and compatibility problems. A few commenters share their own experiences switching between operating systems, with some echoing the author's sentiments and others detailing difficulties they encountered. The overall sentiment leans toward cautious curiosity about WSL's capabilities while remaining unconvinced it's a complete replacement for a native Linux environment for serious development work. Several users suggest the author might switch back to Linux in the future as their needs change.
Summary of Comments ( 991 )
https://news.ycombinator.com/item?id=44031385
Hacker News commenters generally expressed cautious optimism about WSL being open-sourced. Some questioned the GPLv2 license choice, wondering about its implications for driver development and potential future monetization by Microsoft. Others pointed out the limitations of the current open-source release, noting that kernel modifications still require rebuilding from source and expressing a desire for a more streamlined process. Several commenters discussed the benefits of this move for interoperability and developer experience, while others speculated about Microsoft's motivations, suggesting it could be a strategic play to attract more developers to the Windows ecosystem or potentially influence future Linux development. A few expressed concern over the potential for increased complexity and maintenance burden.
The Hacker News post discussing the open-sourcing of WSL (Windows Subsystem for Linux) generated a significant number of comments, with many expressing cautious optimism, excitement, and some skepticism. Several recurring themes and compelling points emerged from the discussion.
Many commenters expressed interest in understanding the motivations behind Microsoft's decision to open-source WSL. Some speculated that it was a strategic move to attract more developers to the Windows ecosystem, leveraging the popularity and power of Linux tools. Others wondered if it was a way to reduce maintenance burden by involving the community, or perhaps a preemptive measure against potential future regulations targeting proprietary components within Windows.
A significant portion of the discussion revolved around the licensing choice (MIT license) and its implications. While generally viewed positively, some commenters raised questions about the practical implications of combining open-source WSL components with the closed-source Windows kernel. Concerns were also raised about the potential for future licensing changes or restrictions, and how this might impact the community's ability to contribute and modify the code.
Several technically-inclined commenters delved into the architecture of WSL and the challenges associated with open-sourcing a component so tightly integrated with the Windows kernel. Discussions touched upon topics like performance implications, driver development, and the potential for future improvements now that the community could contribute. Some commenters expressed hope that the open-sourcing would lead to better integration between Windows and Linux, potentially enabling features like direct hardware access within WSL.
There was notable excitement about the potential for community contributions, with commenters suggesting improvements such as better GPU support, enhanced filesystem integration, and improved compatibility with specific Linux distributions. Some even envisioned the possibility of porting WSL to other operating systems.
However, not all comments were positive. Some skepticism revolved around Microsoft's history with open source and concerns about potential "embrace, extend, extinguish" tactics. Others questioned the long-term viability of the project and the level of commitment Microsoft would maintain.
Finally, some commenters expressed a more general sentiment of surprise and appreciation for Microsoft's evolving approach to open source, contrasting the current open-source friendly approach with the company's historical stance. The open-sourcing of WSL was seen by some as a significant milestone in Microsoft's ongoing transformation and a positive development for the broader software development community.