WSL VS nushell

There have been massive GitHub issue spams recently, including in Microsoft's WSL repository.

https://github.com/microsoft/WSL/issues/40028

Reference: https://github.com/microsoft/WSL/issues/12586

The Windows filesystem isn't slow per se, it's a slowness caused by "a thousand cuts" type of problem.

https://github.com/Microsoft/WSL/issues/873#issuecomment-425...

You might be missing context here.

There is a feature of Windows called “Windows Subsystem for Linux (WSL)” already that basically does the inverse of this (windows host, Linux VM).

https://github.com/microsoft/WSL

The feature is a windows subsystem (for running Linux).

I mean inside WSL. E.g. running nested virtual inside WSL env. https://github.com/microsoft/WSL/issues/11216#issuecomment-2... for details.

I use a WSL backend and there seems to be some issues with file watching (You can read more about it here and here). This means that automatic recompilation on save does not work, this is why I add the --manual-run flag in the initialization. On other systems this might work without issues.

👉 Baixar WSL 2.3.24 (MSI)

Could I introduce you to https://www.nushell.sh/, kind sir?

Started using it last year and being able to type ‘ls | sort-by modified -r | take 5’ feels liberating.

https://fishshell.com/ https://xon.sh/ https://www.nushell.sh/ https://elv.sh/

You're replying to someone that says POSIX shells are holding people back, not that the terminal is a bad idea, there are many alternative shells which offer benefits over POSIX shells. fish-shell has everything you want from an interactive shell included, xonsh is a mix Python shell, nushell and elvish are adding types and other things to shell.

The VT protocols that all shells have to confirm with are pretty dated and I'd love to throw them off the roof for something less stateful and with multiple font sizes but there's no arguing that text based interfaces are good.

Since Zed doesn't have an equivalent extension yet, I decided to replicate the functionality using Nushell (my daily shell of choice).

I think you may enjoy [Nushell](https://www.nushell.sh)

nushell (https://www.nushell.sh/) is essentially perfect for this use case! i use it rather than posix(y) shells for most projects where id normally reach for python.

> And it's a bit sad that in the year of our lord 2025, the best way to get such fundamental information is by using regexes to parse a table[1],

Look at nutshell an see if that gives you what you are looking for https://www.nushell.sh/

Too bad README doesn't show sample commands, discuss design or list differences from existing shells. So... it's just a shell, in Rust? Like fish, but still WIP? And only for redox-os?

In which case, why not just go with nushell https://www.nushell.sh/

If you want to adopt it in your workplace, I would not recommend nushell. They have severe, long standing bugs which don't get fixed. The most annoying to me is output formatting:

https://github.com/nushell/nushell/issues/13601

https://github.com/nushell/nushell/issues/16379

The context of the blog post is that "warts" are the way something was originally designed or built, which is now outdated and you would change it if you could, but you don't want to break backwards compatibility so you don't.

> "For example, some GNU programs like `grep` and `find` support a `POSIXLY_CORRECT` env var, which changes their interface and behavior."

By your own logic that's not a wart, that's the way the programs work and they are documented to work like that. Twisting yourself into knots to pretend Linux/Unix utilities are perfectly designed isn't good logic. There's no excuse "it was designed that way" or "it's documented to work like this" which makes something not warty.

For example unserialised byte streams where you have to fight whether \n or 0 (null byte) are data or record separators, is a wart. How do we know? Because when people design newer tools they don't keep that, they design it away. Serialised JSON and jq, .NET objects in PowerShell, structured data in nushell[1] and oilshell YSH[2].

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

[2] https://oils.pub/ysh.html