Live data from Hacker News

Show HN: I wrote a modern Command Line Handbook

commandline.stribny.name

91–100 of 115 posts

Re: Show HN: I wrote a modern Command Line Handbook

#91

If one reads a book like this and becomes good at the command line. How much do they still need to grok/pickup from devops to be competent at it?

DevOps is not very specific term... so hard to list specific things to learn. But it certainly will be much, much more than just shell/command line knowledge.

Re: Show HN: I wrote a modern Command Line Handbook

#92

Earlier quoted context omitted.

Make is a powerful self-documentable tool. It can hide tons of complicated dependencies implementation details behind a simple and universal CLI.

If you want to use make, power to you, it’s definitely a useful tool. (What I’m trying to say is I’m bashing make, not you.) That being said, I absolutely hate make, there are so many footguns and weird quirks and implicit behavior that always end up biting me. I find that 90% of the time what I actually want is a command runner like Just ( https://github.com/casey/just ) and have the make file contain the absolute s…

These days people have a tendency to grab a latest and shiniest tools when the existing ones are hard to use. Because it takes more effort to understand them than install new ones.

With LLM, we might have a chance to explore the capabilities and deeper ideas in them. If I have enough LLM budget (time and money wise), I might spend more on using awk to build super agents. GNU manuals are perfect context for these kinds of usages.

Re: Show HN: I wrote a modern Command Line Handbook

#93
post #4

Honestly I would’ve liked to fork over cash for a book like this but the deal breaker for me is that it’s in PDF format. I like to read all of my books on a Kindle (with koreader installed) so epub files that can be resized to fit its weird dimensions are a must.

For what it’s worth I would have purchased if this was available in physical form (I’m weighing purchasing anyway, but my personal hunch is I’d pay $20-30 for physical copy and probably $10-20 for pdf).

Amazon makes it quite easy to publish books that get printed on demand, and they accept pdf files as inputs.

Re: Show HN: I wrote a modern Command Line Handbook

#94

Example pages here: https://drive.google.com/file/d/1PkUcLv83Ib6nKYF88n3OBqeeVff...

Page 12 of the example pdf ends with "On Linux, the PATH looks something like this:", but then there's no PATH example shown.

Yes, the linked sample pages are just randomly taken pages from the book PDF, as I put it together quickly for the Show HN. Apologies. I will make a better example when I rework the landing page.

Re: Show HN: I wrote a modern Command Line Handbook

#95
post #4

Honestly I would’ve liked to fork over cash for a book like this but the deal breaker for me is that it’s in PDF format. I like to read all of my books on a Kindle (with koreader installed) so epub files that can be resized to fit its weird dimensions are a must.

For what it’s worth I would have purchased if this was available in physical form (I’m weighing purchasing anyway, but my personal hunch is I’d pay $20-30 for physical copy and probably $10-20 for pdf). Amazon makes it quite easy to publish books that get printed on demand, and they accept pdf files as inputs.

Thanks for the input. I have made several updates to the book in the past and this would be lost in print, but as the book matures and I incorporate feedback it can be interesting to try offering a print version. Perhaps print-on-demand type of thing.

Re: Show HN: I wrote a modern Command Line Handbook

#96

Earlier quoted context omitted.

If you want to use make, power to you, it’s definitely a useful tool. (What I’m trying to say is I’m bashing make, not you.) That being said, I absolutely hate make, there are so many footguns and weird quirks and implicit behavior that always end up biting me. I find that 90% of the time what I actually want is a command runner like Just ( https://github.com/casey/just ) and have the make file contain the absolute s…

These days people have a tendency to grab a latest and shiniest tools when the existing ones are hard to use. Because it takes more effort to understand them than install new ones. With LLM, we might have a chance to explore the capabilities and deeper ideas in them. If I have enough LLM budget (time and money wise), I might spend more on using awk to build super agents. GNU manuals are perfect context for these kind…

A compelling idea, but cmake writing endif(), find_package() being the equivalent of ‘from package import *’, and CXX automatically getting re-named to CMAKE_CXX_COMPILER is just bad design. There’s no deeper idea to explore. The system is just ugly and confusing.

I’ve been reading through https://cliutils.gitlab.io/modern-cmake/README.html to try and get my head around CMake best practices and the book is just line after line of “Don’t do it the old way or the obvious way, because you will end up accidentally doing the wrong thing due to A Hidden Footgun.” That’s bad design*!

Re: Show HN: I wrote a modern Command Line Handbook

#97

Earlier quoted context omitted.

For what it’s worth I would have purchased if this was available in physical form (I’m weighing purchasing anyway, but my personal hunch is I’d pay $20-30 for physical copy and probably $10-20 for pdf). Amazon makes it quite easy to publish books that get printed on demand, and they accept pdf files as inputs.

Thanks for the input. I have made several updates to the book in the past and this would be lost in print, but as the book matures and I incorporate feedback it can be interesting to try offering a print version. Perhaps print-on-demand type of thing.

Amazon does print on demand. I have a book published there that I sell at cost and it’s about $8 shipped. Print quality is pretty good.

If you make changes, you just upload a new template and you’re all set.

Re: Show HN: I wrote a modern Command Line Handbook

#98

Earlier quoted context omitted.

I’m excited about this book and appreciate your work! One thing that was distracting was the large title font when I tried to view this site in portrait mode on mobile, as some of the letters are cut off. If that could be fixed, it would help ensure people stay engaged and read it. You could also potentially use an LLM or something like Grammarly to help proofread it (not edit it). This is very cool!

Thank you! Yes, as other people pointed out too, the landing page could do with some mobile and copy improvements.

A note on English: "Fresh off the press" is the colloquialism you're looking for, not "Fresh out of press."

Re: Show HN: I wrote a modern Command Line Handbook

#99

Earlier quoted context omitted.

These days people have a tendency to grab a latest and shiniest tools when the existing ones are hard to use. Because it takes more effort to understand them than install new ones. With LLM, we might have a chance to explore the capabilities and deeper ideas in them. If I have enough LLM budget (time and money wise), I might spend more on using awk to build super agents. GNU manuals are perfect context for these kind…

A compelling idea, but cmake writing endif(), find_package() being the equivalent of ‘from package import *’, and CXX automatically getting re-named to CMAKE_CXX_COMPILER is just bad design. There’s no deeper idea to explore. The system is just ugly and confusing. I’ve been reading through https://cliutils.gitlab.io/modern-cmake/README.html to try and get my head around CMake best practices and the book is just line…

We can use LLM to read and write cmake as well. They are all Turing machines anyway.

Re: Show HN: I wrote a modern Command Line Handbook

#100

Earlier quoted context omitted.

If you want to use make, power to you, it’s definitely a useful tool. (What I’m trying to say is I’m bashing make, not you.) That being said, I absolutely hate make, there are so many footguns and weird quirks and implicit behavior that always end up biting me. I find that 90% of the time what I actually want is a command runner like Just ( https://github.com/casey/just ) and have the make file contain the absolute s…

I agree too, Just (and others) are better as a pure entry point. But when you come to projects that already have Makefiles, or you know you have just one less thing to install in a container... you use Make.

In the era of micro services and ephemeral computing runtime, the baseline default environment will save us from unnecessary complexity.

For example, in CI pipelines, I can use my own plain. Makefile to replace different yaml tasks across different languages, from shell scripts to python scripts to npm scripts.

Post reply on HN