cross-posted from: https://sh.itjust.works/post/5850736

This is the resource I've been looking for. I'm working my way through the book but it gets in the weeds really early. It's all fun and games and then chapter 4 just hits like a brick wall. Amos does a tremendous job explaining the why behind things, in a more wheels to the pavement way.

  • maegul (he/they)@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    the file system has a lot of failure cases

    Oh for sure, like I said this makes a lot of sense. All I was saying was that as a pitch for learning the language, the part after the file read had been sorted was much more compelling and interesting.

    • Ogeon@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Absolutely, I didn't mean to suggest otherwise. :) I'm just giving a bit of context and perspective from someone who has used it for a while.