Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

An Illustrated Guide to Useful Command Line Tools

wezm.net

Post reply on HN
Print view View original

31–40 of 108 posts

Re: An Illustrated Guide to Useful Command Line Tools

#31

Post by epage »

degraafc wrote: post #10
naikrovek wrote: post #2

Amazing how many of those are written in Rust and Go.

I don't think it says much about the tools themselves though, it just makes sense when you look at the author's GitHub and see a bunch of Rust projects.

I think there are a couple of relevant factors

- Can be distributed as a single binary, not requiring an interpreter and virtual environment. - Being more fun to make a hobby tool in due to minimal footguns compared to C/C++. - Really good dependency management and build tool making it easy to compose these CLIs out of powerful building blocks (at east for Rust). For example, ripgrep is broken up into a lot of packages that you can compose together to make your own custom tool.

Re: An Illustrated Guide to Useful Command Line Tools

#32

Post by atonalfreerider »

An observation: I have always taken the meaning of the word "illustrated" to specifically refer to non-lexical graphics. Searching the dictionary definition of the word, I find a looser definition that applies to "examples" intended to aid an explanation.

This is a similar cognitive dissonance to when I first learned that "Visual Basic" and "Visual Studio" meant that the syntax of the displayed code was highlighted, not graphically represented in a non-lexical way.

Re: An Illustrated Guide to Useful Command Line Tools

#34

Post by mysterydip »

atonalfreerider wrote: post #32

An observation: I have always taken the meaning of the word "illustrated" to specifically refer to non-lexical graphics. Searching the dictionary definition of the word, I find a looser definition that applies to "examples" intended to aid an explanation. This is a similar cognitive dissonance to when I first learned that "Visual Basic" and "Visual Studio" meant that the syntax of the displayed code was highlighted,…

I believe Visual Basic/Studio referred tonthe addition of WYSIWYG GUI creation tools and event binding to the languages.

Re: An Illustrated Guide to Useful Command Line Tools

#35

Post by cauthon »

aquova wrote: post #18

I quite like this list, there are a number of utilities here that I already use on a daily basis. There are also a few utilities that I like that weren't on this list, or some alternatives to what was shown. Some off the top of my head: - nnn[0] (C) - A terminal file manager, similar to ranger. It allows you to navigate directories, manipulate files, analyze disk usage, and fuzzy open files. - ncdu[1] (C) - ncurses d…

Seconding ncdu! The interface is great, and I like that it’s modular so you can run the disk usage component as a cronjob and then have a nightly snapshot readily accessible

Re: An Illustrated Guide to Useful Command Line Tools

#36

Post by Sharlin »

atonalfreerider wrote: post #32

An observation: I have always taken the meaning of the word "illustrated" to specifically refer to non-lexical graphics. Searching the dictionary definition of the word, I find a looser definition that applies to "examples" intended to aid an explanation. This is a similar cognitive dissonance to when I first learned that "Visual Basic" and "Visual Studio" meant that the syntax of the displayed code was highlighted,…

I’ve always assumed that the ”Visual” in VB and others refers to the WYSIWYG drag’n’drop interface for creating GUIs.

Re: An Illustrated Guide to Useful Command Line Tools

#38

Post by dickeytk »

Sharlin wrote: post #36
atonalfreerider wrote: post #32

An observation: I have always taken the meaning of the word "illustrated" to specifically refer to non-lexical graphics. Searching the dictionary definition of the word, I find a looser definition that applies to "examples" intended to aid an explanation. This is a similar cognitive dissonance to when I first learned that "Visual Basic" and "Visual Studio" meant that the syntax of the displayed code was highlighted,…

I’ve always assumed that the ”Visual” in VB and others refers to the WYSIWYG drag’n’drop interface for creating GUIs.

Same here—though for the same reason I always thought "VSCode" was a strange name since it doesn't have any of those interfaces.

Re: An Illustrated Guide to Useful Command Line Tools

#39

Post by eurg »

wodenokoto wrote: post #3

Can someone explain the misuse of cat, which bat solves?

Catting a file will your terminal make interpret escape codes in the file.

For instance:

    $ echo -e "\033]0;${USER} is an unfriendly person\007" > test-file.txt
Then, many days later:

    $ cat test-file.txt
will change your terminal title.

With less, you _can_ interpret escape codes, but usually you don't, and I consider this the correct default.

Re: An Illustrated Guide to Useful Command Line Tools

#40

Post by kyberias »

Sharlin wrote: post #36
atonalfreerider wrote: post #32

An observation: I have always taken the meaning of the word "illustrated" to specifically refer to non-lexical graphics. Searching the dictionary definition of the word, I find a looser definition that applies to "examples" intended to aid an explanation. This is a similar cognitive dissonance to when I first learned that "Visual Basic" and "Visual Studio" meant that the syntax of the displayed code was highlighted,…

I’ve always assumed that the ”Visual” in VB and others refers to the WYSIWYG drag’n’drop interface for creating GUIs.

But... they do refer to that.
Post reply on HN