Hacker News Reader

Comment by danso | Hacker News Reader

This likely will be just another book on the long list of books I've owned but don't get through, but hard to ignore a 700-page book with a topic both esoteric and pragmatic (I use git daily but have very little knowledge of it beyond what commands to Google). And one in Ruby -- a language I almost never use today, or really see, but definitely grew up with.

View on HN

The desire to buy more books than you can ever read is so universal, there's a Japanese word for it: Tsundoku

I wonder what the Japanese is for endless scrolling of a Kindle directory?

Tsundokindle

Yeah I'm interested in this topic too, but there's very little chance that I will go through a 700 page e-book.

I'm probably old-fashioned, but it seems like too much "screen time".

I have about five 500- to 1000-page dead-tree compiler books, and many (most) of them have sat around unread for months or even a few years -- at first.

But over time I've managed to get through significant portions of them. That's probably because they are laying around near my couch. The sight of them reminds me why I bought them :) I find the paper books more ergonomic to skim.

In contrast, I feel like an e-book would just get lost on my iPad. This feedback might not be actionable but I thought I'd share...

The free chapter "Reshaping history" looks like a reprint of the publicly available information about rebasing from the Git Book. It doesn't really showcase the main book premise of teaching fundamental data structures and engineering concepts used in Git.

if you go through the files in the repo they are very easy to read (I would recommend starting with the test/ folder): https://github.com/jcoglan/jit

obviously the lib folder requires a lot of git-specific knowledge but I didn't see any use of features that don't have exact or very similar equivalent in more popular programming languages.

I think the most "complex" might be things like Struct.new(*Inputs::ATTRS) where it's creating a new anonymous class from a list of attributes which becomes the class instance attributes (nothing crazy :) )

Reply on news.ycombinator.com