News for hackers. Stuff that matters.

A comment on On Cache Invalidation: Why Is It Hard? (2018).

Re:On Cache Invalidation: Why Is It Hard? (2018) by breakingcups on Monday April 05, 2021 @07:03AM (#26697503)
> There are only two hard things in Computer Science: cache invalidation and naming thing.

I've always heard it as "There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors."

[ Parent | on HN ]
Re:On Cache Invalidation: Why Is It Hard? (2018) by darkerside on Monday April 05, 2021 @09:25AM (#26698594)
Nitpick but I've always preferred to say it as "naming things and cache invalidation" in that order, which IMO emphasizes the irony of creating labels for things and then needing to forget about them.
[ Parent | on HN ]
Re:On Cache Invalidation: Why Is It Hard? (2018) by timhwang21 on Monday April 05, 2021 @10:46AM (#26699712)
"Cache invalidation, naming things and off-by-one errors. And cache invalidation."
[ Parent | on HN ]
Re:On Cache Invalidation: Why Is It Hard? (2018) by GuB-42 on Monday April 05, 2021 @02:18PM (#26702544)
Don't race forget conditions about.
[ Parent | on HN ]
Re:On Cache Invalidation: Why Is It Hard? (2018) by murph-almighty on Monday April 05, 2021 @11:08AM (#26700027)
That's clever!

I think off-by-one errors got a bit easier once we started normalizing loops like `for cat in cats`, but that doesn't really fly when you need to do multiple array accesses while iterating through the loop, so I suppose they're here to stay...

[ Parent | on HN ]
Re:On Cache Invalidation: Why Is It Hard? (2018) by asimpletune on Monday April 05, 2021 @11:05AM (#26699979)
Wow that’s pretty funny. I’m going to use that someday.
[ Parent | on HN ]