Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

If you like Powershell but have some complaints, you might find nushell to be the best of both worlds. My elevator pitch for it would be imagine the object-oriented / typed nature of Powershell, minus the verbosity and windows-centric design of it. As someone who develops on and for windows computers, nushell is a real breath of fresh air.




I have a command line program at work which outputs json. Pure JSON in all situations.

I thought nushell would be able to make sense of that and display it semi-nicely.

Nushell pukes on it, errors out, and doesn’t even show the output of the command. As far as sins go for a shell, not showing the output of the program it just ran is very high among them.

nushell had its chance with me.


With external commands you might have to collect the output of the program before doing any sort of manipulation. I’ve been got by this before too; the fix is simple (for me at least). `external.exe | collect | from json` et voila

This doesn't look like a pit of success design.

Well, every shell has its quirks and gotchas. I’ve found nushell’s to be the least intrusive and most workable thus far.

Whenever someone recommends nushell, I feel like I have to point out that its table output (a core feature) is broken:

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

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




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: