CLI: Improved • Hacker News Board

Re: CLI: Improved

#81

Post by vram22 » Thu, Aug 30, 2018, 9:45 PM UTC

earenndil wrote: post #44

burntsushi wrote: post #33

Earlier quoted context omitted.

If you don't mind me asking, in roughly what cases do you reach for grep instead of ag || ack? Is it a familiarity thing, or specific features or something else?

Not the gp, but I generally use ripgrep when I want to find something manually, and regular grep in a script.

Why? Does ripgrep not work as well (or better) than grep in a script? And if so, why not?

Or is because you deploy your scripts to other machines where ripgrep may not be present, but grep will?

Re: CLI: Improved

#82

Post by topspin » Thu, Aug 30, 2018, 9:47 PM UTC

orf wrote: post #29

Is anyone else impressed with the quality (and speed!) of some of the tools written in Rust? I'm an avid user of fd and bat, the former being ridiculously fast. Often I find something on github, I'm impressed by the quality of the documentation, features, UI etc, then lo and behold it's written in Rust. Another one potentially for this list is tokei[1] I was trying to count the code in our repos at work and used the…

tokei is actually the very first Rust program that I found 'in the wild' while searching for a tool. I had run many Rust programs prior to then, but they had always been in the context of experimenting with Rust.

Re: CLI: Improved

#83

Post by IshKebab » Thu, Aug 30, 2018, 9:48 PM UTC

FactolSarin wrote: post #26

patja wrote: post #14

"I'm not sure many web developers can get away without visiting the command line." IIS has significant market share. I'll bet most web developers who deploy on it get away without having to use the command line interface very often if at all. https://news.netcraft.com/archives/2018/08/24/august-2018-we...

I have co-workers who work on a big intranet web application that runs on IIS, and they never touch it. They recently finally switched to git for source control, and they want to do everything via GUI. I've tried to show them how some things are just easier/better from the command line, but if something isn't doable via GUI, they won't do it. One of them keeps committing line endings differently than everyone else, a…

Git has such a terrible command line that most things are easier in (good) GUIs than on the command line.

The only exceptions I can think of are interactive rebase which has a weirdly good command line interface and is really confusing in every GUI I've tried; and continuing/aborting rebase and cherry picks when there is a conflict. And that's only because most GUIs don't bother to actually implement that properly and mislead you into thinking that you should make a new commit.

Re: CLI: Improved

#84

Post by jolmg » Thu, Aug 30, 2018, 9:48 PM UTC

vram22 wrote: post #81

earenndil wrote: post #44

Earlier quoted context omitted.

Not the gp, but I generally use ripgrep when I want to find something manually, and regular grep in a script.

Why? Does ripgrep not work as well (or better) than grep in a script? And if so, why not? Or is because you deploy your scripts to other machines where ripgrep may not be present, but grep will?

Scripts tend to be shared, so portability matters. grep alternatives, while great for interactive use, are generally not worth being an extra dependency to install.

Re: CLI: Improved

#85

Post by vram22 » Thu, Aug 30, 2018, 9:51 PM UTC

orf wrote: post #29

Is anyone else impressed with the quality (and speed!) of some of the tools written in Rust? I'm an avid user of fd and bat, the former being ridiculously fast. Often I find something on github, I'm impressed by the quality of the documentation, features, UI etc, then lo and behold it's written in Rust. Another one potentially for this list is tokei[1] I was trying to count the code in our repos at work and used the…

Have you done any comparison (even informal) of similar tools written in Rust and Go?

Re: CLI: Improved

#86

Post by euank » Thu, Aug 30, 2018, 9:52 PM UTC

bronlund wrote: post #48

I was wondering if any of you use alternatives or hacks for the cd command? I've been testing out a couple of different ones, like xd, fcd, wcd and pushd/popd, but I'm not quite sure which I should commit to or if there are better ways :)

I can recommend pazi as a convenient tool for zapping around https://github.com/euank/pazi

The readme also lists several alternatives in the same space as pazi.

Re: CLI: Improved

#87

Post by thethirdone » Thu, Aug 30, 2018, 9:56 PM UTC

the8472 wrote: post #73

orf wrote: post #29

Is anyone else impressed with the quality (and speed!) of some of the tools written in Rust? I'm an avid user of fd and bat, the former being ridiculously fast. Often I find something on github, I'm impressed by the quality of the documentation, features, UI etc, then lo and behold it's written in Rust. Another one potentially for this list is tokei[1] I was trying to count the code in our repos at work and used the…

I had a case where tar was too slow for my needs. Rust did let me cobble the right syscalls and threads together to make it more HDD-friendly and faster while forcing me to handle all the gritty filesystem error cases from the start. Lo and behold, about 4 times faster on an idle system and orders of magnitude faster on a busy system. It just would not have been possible to do it by combining shell utilities and too…

Do you have the code posted online? I would like to take a look through it.

Re: CLI: Improved

#88

Post by earenndil » Thu, Aug 30, 2018, 9:58 PM UTC

vram22 wrote: post #81

earenndil wrote: post #44

Earlier quoted context omitted.

Not the gp, but I generally use ripgrep when I want to find something manually, and regular grep in a script.

Why? Does ripgrep not work as well (or better) than grep in a script? And if so, why not? Or is because you deploy your scripts to other machines where ripgrep may not be present, but grep will?

Grep is:

* Deterministic

* Standard

* Written in c

* Equally performant (where it matters)

* Doesn't show colour or line numbers unless I tell it to

* Doesn't watch .gitignores unless I tell it to

Re: CLI: Improved

#89

Post by the8472 » Thu, Aug 30, 2018, 9:59 PM UTC

thethirdone wrote: post #87

the8472 wrote: post #73

Earlier quoted context omitted.

I had a case where tar was too slow for my needs. Rust did let me cobble the right syscalls and threads together to make it more HDD-friendly and faster while forcing me to handle all the gritty filesystem error cases from the start. Lo and behold, about 4 times faster on an idle system and orders of magnitude faster on a busy system. It just would not have been possible to do it by combining shell utilities and too…

Do you have the code posted online? I would like to take a look through it.

https://github.com/the8472/fastar

Re: CLI: Improved

#90

Post by xxpor » Thu, Aug 30, 2018, 9:59 PM UTC

orf wrote: post #29

Is anyone else impressed with the quality (and speed!) of some of the tools written in Rust? I'm an avid user of fd and bat, the former being ridiculously fast. Often I find something on github, I'm impressed by the quality of the documentation, features, UI etc, then lo and behold it's written in Rust. Another one potentially for this list is tokei[1] I was trying to count the code in our repos at work and used the…

I'm surprised they said ack || ag over ripgrep. I'm a total convert. It's AMAZINGLY fast.