WSL VS Windows Terminal

👉 Baixar WSL 2.3.24 (MSI)

Microsoft's DirectX C++ example code needs to interact with DirectX' C APIs. That will easily lead to "C with classes" C++ when most of the code is interacting with foreign APIs, like these API demos do.

I think open-source software like https://github.com/microsoft/WSL is probably more representative of what modern C++ companies look like. Plenty of files that just interact with OS C APIs, but no shortage of modern C++ features in use.

Microsoft continues to be a major contributor to open source and announced a couple major projects moving from closed-source to the open on GitHub. The first is a long-time coming project, the Windows Subsystem for Linux (WSL). I first used WSL to port a Java stack to Windows. That stack was a nightmare to run on Windows due to a team optimizing for macOS workflows but we wanted to enable new developers to use standard Windows dev machines and stop requiring expensive macOS hardware for a cross-platform native toolchain like Java. Today, WSL is a major part of the Windows developer experience. And now, Microsoft is open-sourcing WSL to allow the community to contribute and innovate on the project on GitHub.

https://github.com/microsoft/WSL/issues/9049#issuecomment-26...

WSL GitHub Repository

https://github.com/microsoft/WSL/issues/7973#issuecomment-27...

Is there a way to push this without tripping the corporate auto-close bot?

If you are running Microsoft Windows, I want to advise one more prerequisite step that you need to take before getting started with Python or uv: install the Windows Subsystem for Linux, also known as WSL2. Do not, for the love of all that is good and holy, try and install Python tooling directly in Windows; install WSL first. This guide outlines all the steps you need to take to get started, though I recommend downloading WSL from the Releases page on Github instead of from the Microsoft Store as advised in Step 3.

Please fix this issue: https://github.com/microsoft/terminal/issues/16921 (or better yet, rewrite the whole thing in Rust)

Microsoft Terminal

[^1]: https://github.com/microsoft/terminal/issues/10362#issuecomm...

Some parts already have been open-sourced. For example, the console host component has been open sourced here: https://github.com/microsoft/terminal

And the FAT filesystem driver: https://github.com/microsoft/Windows-driver-samples/tree/mai...

Maybe they could consider an Apple-style approach: open source the core of the kernel and text-mode user space but leave the GUI closed.

Of course, open sourcing everything would be even better, but that might too big of a step for them. Open sourcing the non-GUI core could be a good initial step, whether or not it ends up going further.

cmd.exe or the new https://github.com/microsoft/terminal ?

A quick off-the-cuff remark based solely on the title: in 2024, I think the state of the terminal has never been better, in large part to Microsoft making a high quality terminal easily available to everyone on Windows [1]

As an application author, I love being able to assume that all major platforms have a good terminal and that my favorite terminal rendering libraries should Just Work on all of them

[1] https://github.com/microsoft/terminal