Live data from Hacker News

GitHub – nushell/nushell: A new type of shell

github.com

121–130 of 411 posts

Re: GitHub – nushell/nushell: A new type of shell

#121
post #102
post #30

Earlier quoted context omitted.

powershell for unix is ... powershell: https://docs.microsoft.com/en-us/powershell/scripting/instal...

Am I missing something cool by not looking into PowerShell for Linux? Anyone using it could chime in and share how it improves their workflow? What kind of tools does it bring to the table?

I use it a bit on windows servers because it integrates well with other microsoft tools.

On linux...it seems both redundant and just plain weird for weirds sake. There are literally dozens of alternatives on linux that have a sane syntax and are likely preinstalled.

Re: GitHub – nushell/nushell: A new type of shell

#122

The title is somewhat misleading and makes it seem like this is a GitHub company initiative rather than a project just hosted on GitHub. I've not seen this title format on HN before. Could it be changed?

The title is the actual value of the title html tag on the page

Re: GitHub – nushell/nushell: A new type of shell

#123
post #71
post #45

Earlier quoted context omitted.

Try fish shell. It has auto completion by default and is easy to configure with web interface "fish_config", no need to rely on some community repo like oh-my-zsh. There can be bugs if you set it as default shell but i just append "fish" at the end of my .bashrc :)

It's so interesting - it seems that fish is getting more and more popular lately. I tried it ~7 years ago and thought it was severely lacking, so I just stuck with zsh and have never really had a reason to look back. Maybe I'll check out fish again at some point - what features does it have that drew you to it?

not OP but the two features of fish that stood out for me so much that I make it my default shell on remote servers are

1) the autocomplete suggestion as you type a command [1]

2) scrolling thru commands after partially writing one only shows entries that match the written text

3) knowing if a command will work before pressing enter -- saves from a lot of gotchas.

all of these read like features nice to have but not essential, but when you're using something every day, it's worth it :)

[1]: https://fishshell.com/docs/current/tutorial.html#autosuggest...

Re: GitHub – nushell/nushell: A new type of shell

#124

The title is somewhat misleading and makes it seem like this is a GitHub company initiative rather than a project just hosted on GitHub. I've not seen this title format on HN before. Could it be changed?

The title is the actual value of the title html tag on the page

Heh, that's interesting: When you're logged in, the title tag changes to drop the "GitHub -" prefix.

Re: GitHub – nushell/nushell: A new type of shell

#125

The title is somewhat misleading and makes it seem like this is a GitHub company initiative rather than a project just hosted on GitHub. I've not seen this title format on HN before. Could it be changed?

I think the "nushell/nushell" part makes it clear which repo it is talking about.

Re: GitHub – nushell/nushell: A new type of shell

#126

Earlier quoted context omitted.

"A new type of shell" is a bit of marketing text to express the fact that this shell doesn't follow in the footsteps of most other shells (bash, zsh, fish, etc) in terms of treating things as blobs of text (which allows for a number of innovations). The fact that the author even states that it's partially inspired by Powershell demonstrates that he's aware of the similarities (and has in fact cribbed many ideas from…

Ah, I see. Thank you for explaining. The part that bothered me was not that they described something that shared some concepts with PowerShell as "a new kind", but that I did not see any illustration of entirely novel features in the examples that followed. As a sibling comment remarked, they feel I'm quite mistaken, and there are very positive distinctions illustrated in the examples, but I took a look at them again…

It's not a question of precision, but rather one of convention. In this case, the convention is that a marketing line glosses over huge swaths of reality in order to give a simple and compelling narrative (people like things to appear simple, even if they're not - and even if they KNOW they're not). So calling out imprecisions and inaccuracies in this context reflects poorly upon you because everyone is already aware of the unspoken assumptions being made, and take criticisms about things already covered by the assumptions as unnecessary and irritating pedantry. As in a "Yes, we KNOW that it's not technically 100% accurate, please stop being annoying." sort of response.

From my impression of your word choice and sentence structure, I'm making the assumption that you have autistic traits, which is why I'm explaining in more detail and on a social level.

Re: GitHub – nushell/nushell: A new type of shell

#128

The title is somewhat misleading and makes it seem like this is a GitHub company initiative rather than a project just hosted on GitHub. I've not seen this title format on HN before. Could it be changed?

I think the "nushell/nushell" part makes it clear which repo it is talking about.

I didn't find it clear, I also thought it was a GitHub project.

Re: GitHub – nushell/nushell: A new type of shell

#129
post #67

Earlier quoted context omitted.

Were you not able to before? ls | grep foo | sort is hardly something people normally read the man page for.

This isn't the way I'd sort ls output by date or whatever field. I'd use `ls -l --sort=date` which I guess is what the GP meant with having every tool do their own sorting by field. In nushell one can just do `ls | sort-by size`

Yes, that is what I mean.

I also like that nushell's table oriented approach displays the column names, and you just use those names for the `sort` command or `where` command etc.

Re: GitHub – nushell/nushell: A new type of shell

#130
post #4

Kudos for writing something in rust and not appending "written in rust!" everywhere.

Why is everything written in rust nowadays? Apart from the safety it provides.

> Apart from the safety it provides.

Sum types (and pattern matching), first-class results, ownership, good performances and a rich ecosystem turn out to be quite nice for a general purpose langage once you’ve passed the hurdle of the borrow checker, even ignoring all the zero-cost abstraction stuff.

Also the really solid and safe multithreading. You might struggle a bit getting all your ducks in a row, but past that you’re reasonably safe from all sorts of annoying race conditions. And rayon is… good.

Not sufficient for GUI applications where the rust experience remains not great, but for CLI or even TUI?

I’ll misquote something i recently saw on Twitter because it’s very much my experience: “and once again I end up riir-ing a one-off tool I wrote in python and wonder why I didn’t just do that from the start”.

Post reply on HN