WSL VS nushell

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

Since everyone is sharing shells written in Rust, I've become quite fond of Nushell: https://www.nushell.sh/

I'd love to see more shell exploring things beyond POSIX. Text based stdin/stdout will always have its place, but having ways to express, serialize, and pass along data in more structured ways is quite nice.

I'm an incredibly happy user of nushell, which brings all the best features of bash and all the best features of more well designed scripting languages in one awesome package that also comes with editor (LSP) support and excellent documentation

https://www.nushell.sh/

(The intro page may be a bit misleading. You can freely mix-and-match existing, unstructured as well as nushell-built-in structured commands in the pipeline, as long as you convert to/from string streams - its not mandatory to use the structured built-ins. For example if an existing cli tool has json output, you can use `tool | from json` to turn it into structured data. There are also commands like `detect columns` that parses classic column output, and so on - the tools to mix-and-match structured and unstructured data are convenient and expressive)

Best thing I've found recently is nushell[0], paired with jc [1] it's pretty much the best shell I've ever used.

[0] https://www.nushell.sh/

REPL-ify your command line then? There's nothing that says you have to be stuck on bash for your command line needs. https://www.nushell.sh/

Nearly all my developer tools are open-source projects written in Rust (Nushell, Helix, WezTerm, and more).

Have you tried nushell (https://www.nushell.sh/)? It embeds GNU coreutils written in Rust, so it feels like Linux even on a Windows machine.

> Another example is jq. I use it occasionally, and ChatGPT handles the syntax pretty well. For me, learning it properly just isn’t worth the time or effort.

This resonates with me, I was in exactly the same position when I needed to do something with `kubectl` JSON output - just ask ChatGPT because I couldn't be bothered to learn the unintuitive syntax.

Interestingly I _can_ blame the tool, because I started using Nushell[1] which has built-in JSON manipulation that provides a MUCH simpler syntax, and I have learnt this properly because it was that easy.

1: https://www.nushell.sh/

But these fantasy consoles are aimed largely at the classic BASIC use case of writing simple games. My interest, meanwhile, is in replacing my shell. I want a BASIC that can be a useful, productive stand-in for bash. In this sense, I'm actually more influenced by new-school shells like nushell, elvish and PowerShell.