Live data from Hacker News

Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

news.ycombinator.com

141–146 of 146 posts

Re: Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

#141
post #136

Earlier quoted context omitted.

I didn't learn Bash from scratch. I just serach Google/StackOverflow for similar questions. But that is the point, there are too many commands to do the same job in Bash, each with dozens of flags. It is hard to learn them all, or even find the right command (like shopt, read) or flag (like -rd, print0, -execdir) in the first place. That's why Nutshell will be simpler for small tasks.

No, the point is that if you go into a discussion saying: "X is better than Y but I should warn you that I never bothered learning Y but instead spent my time learning X" your ability to provide an accurate comparison is already put into question. Then you go on and provide examples of extremely sub-optimal Y code and compare it to X code you wrote. It's very uncharitable and very difficult to tell what is actually b…

You miss the part about them saying that the code is from stackoverflow so in other words not exactly hacked together.

Overall I agree with both of you but on different points, she'll scripting is an outdated painful process and yes we should provide optimal answers to be fair.

Re: Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

#142
post #141

Earlier quoted context omitted.

No, the point is that if you go into a discussion saying: "X is better than Y but I should warn you that I never bothered learning Y but instead spent my time learning X" your ability to provide an accurate comparison is already put into question. Then you go on and provide examples of extremely sub-optimal Y code and compare it to X code you wrote. It's very uncharitable and very difficult to tell what is actually b…

You miss the part about them saying that the code is from stackoverflow so in other words not exactly hacked together. Overall I agree with both of you but on different points, she'll scripting is an outdated painful process and yes we should provide optimal answers to be fair.

I don't think the code presented was taken directly from stackoverflow, and I don't think that's what the person I replied to said. That being said, even if it was from stackoverflow, stackoverflow is a poor resource for older languages/environments. There's still a major focus on points over quality answers and you get lots of bad advice from there.

Re: Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

#143

Earlier quoted context omitted.

Best feature of fish is the fact that my fish dotfiles are about 100loc max with a fully async prompt. Comparable functionality in zsh would be 500loc of ultra obscure tweaks :)

What do you mean by "fully async prompt"?

https://github.com/mattgreen/lucid.fish

It avoids pauses when doing `git status` on gigantic repos.

Re: Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

#144
post #47

I use `fish` as my main shell. It's closer to POSIX than eshell or oil, but it's definitely not POSIX. Personally, the main thing I like about it is that I can't copy paste bash commands. It forces me to read and understand and then convert. It also has some quality of life stuff I really like. I think next time I'm just going to go back to ZSH though as I feel I have learnt enough from the experience of using it tha…

Another fish user reporting in. I don't care too much about bash compatibility. I don't even care shell scripting in my shell - when I need to write a script I write a sh script (or python for more complex ones). I just want a shell that's easy to use and user friendly. For some reason none of the other alternative shells "click" for me - I love the idea of having objects in my shell (like in nushell, or powershell),…

Also a fish user, the lack of bash compatibility if required is easily fixed by bash -c, or just dump it into a script with a bash shebang but most simple one liners can easily be tinkered with to make it fish compatible - case in point `for` which just needs an end in most cases

Re: Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

#145
I was all ready to jump in with nu but I can't live without control-Z and `foo &` :-(

https://github.com/nushell/nushell/issues/4564#issuecomment-...

And coming back to this after all this time, it seems the nushell issue tracker is not getting groomed at all -- are the authors starting get tired of it? https://github.com/nushell/nushell/issues/4320 lists a huge number of duplicates.

Re: Ask HN: Are alternative (oil, nu, etc.) shells usable as daily drivers?

#146

I use `fish` as my main shell. It's closer to POSIX than eshell or oil, but it's definitely not POSIX. Personally, the main thing I like about it is that I can't copy paste bash commands. It forces me to read and understand and then convert. It also has some quality of life stuff I really like. I think next time I'm just going to go back to ZSH though as I feel I have learnt enough from the experience of using it tha…

I use fish too. My favourite feature is typing part of a command and using up and down arrows to cycle through the results, as opposed to ctrl+R and...I don't remember which one. Functions are easy to define too.

ctrl+R and...you keep pushing it to go back in time. In case anyone needs to know.
Post reply on HN