True, because most of them either add a million diagrams or a million copy-pasted source code snippets. And this happens because people "respect" a thick book when they are looking for a technical book. It's quite silly, actually :)
It's kind of strange, considering that most of the non-fiction books I remember most fondly, are fairly thin. The big tomes tend to largely be forgettable (there are of course exceptions) - I guess often because they go into too much detail that date rather than concisely describing concepts.
True, because most of them either add a million diagrams or a million copy-pasted source code snippets. And this happens because people "respect" a thick book when they are looking for a technical book. It's quite silly, actually :)
Somewhat tangentially related, I would like to know how the parent poster or for that matter printed the document.
somewhat unrelated, I don't use emacs but is there a way to break lines such as
#+caption: [[https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux....]
in the org mode source? https://blog.lizzie.io/linux-containers-in-500-loc.org
You can export from org to pdf (type C-c C-e l p in emacs). For some fine tuning you can export to tex and then use pdflatex.
It's kind of strange, considering that most of the non-fiction books I remember most fondly, are fairly thin. The big tomes tend to largely be forgettable (there are of course exceptions) - I guess often because they go into too much detail that date rather than concisely describing concepts.
Because many of us needed to thrust our work to thick books on the days before ubiquitous Internet. :)