WSL VS mkcert

👉 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.

There is also mkcert by Filippo Valsorda (no relation to mkcert.org) at https://github.com/FiloSottile/mkcert

Mkcert is a simple zero-config tool to make locally trusted development certificates with any names you'd like.

Interesting, just checked out if mkcert (the popular way of doing this) supports it and found two issues:

https://github.com/FiloSottile/mkcert/issues/131

https://github.com/FiloSottile/mkcert/pull/113

Hopefully Filippo revisits this now that it's broadly supported.

mkcert

Installation instructions for other operating systems are available at the mkcert GitHub page.

mkcert can help with this! https://github.com/FiloSottile/mkcert

As one-time-setup you’ll need to serve the ROOTCA.pem from the Pi and download and install it on the iPad, but once you’ve done this once, any certs you generate on the Pi will be accepted by the iPad.

mkcert has enabled so many crazy setups and workflows for me over the years, it’s truly fantastic.

mkcert might be getting this as well: https://github.com/FiloSottile/mkcert/pull/309/commits/92215... (this is linked from the current submission's readme)

I use https://github.com/FiloSottile/mkcert for my internal stuff.