5 ms·

to be fair, cache invalidation is hard.

by nthj 14y ago

drivebyacct2 14y ago
And naming things.
- Laremere 14y ago
  Together with off by one errors, they're the two hardest things in computer science...
  - alexkus 14y ago
    Yes, the three hardest things in Comp Sci are cache invalidation and off by one errors.
    - keesj 14y ago
      Don't you mean the 10 hardest things?
      - jamesrom 14y ago
        I think he means the 11 hardest things actually.
        alexkus 14y ago
        10 in ternary (which I think was his part of the joke)
mibbitier 14y ago
All they need to do is add a new "message" to say "y'know that message number 4029375 in the cache, yeah that ones deleted, ignore it". This is not hard.
- natrius 14y ago
  This arrogance is baffling. What makes you think you know enough about Facebook's infrastructure to make such a claim?
  - mibbitier 14y ago
    huh? Infrastructure is totally and utterly irrelevant to the problem. I know enough about common sense to make such a claim. Just send a new message, exactly as you would post an original item/comment/etc, but have some special text/field in there that says "please ignore the previous message". The UI would then hide the previous message. eg COMMENT: {id:9374758, from:"mibbitier", data:"I hate you all!"} COMMENT: {id:9374759, from:"mibbitier", data:"*IGNORE_MESSAGE_IN_UI* 9374758"} Nothing whatsoever to do with infrastructure. Nothing to do with caches. Purely to do with the UI. Not rocket science. Granted, it's a poor way to do it, but it's better than nothing, and easier than trying to invalidate caches etc
    - mh- 14y ago
      I'm sure it's already rendered to a static presentation-level (HTML/template language du jour) form at that point. That wouldn't work.
      - mibbitier 14y ago
        Just put some more javascript in there to deal with it. I'm sure it's not the hardest problem in the world.
        engtech 14y ago
        Great, you've hidden the message with javascript, but now it's still in view-source and in search results for bots. It's also still visible if someone is using noscript (actually, I have no idea if Facebook works with noscript, probably not). The solution you are suggestion doesn't solve the problem and injects more corner cases.
    - 14y ago

to be fair, cache invalidation is hard.

by nthj 14y ago

to be fair, cache invalidation is hard.

drivebyacct2 14y ago

And naming things.

Laremere 14y ago
Together with off by one errors, they're the two hardest things in computer science...
- alexkus 14y ago
  Yes, the three hardest things in Comp Sci are cache invalidation and off by one errors.
  - keesj 14y ago
    Don't you mean the 10 hardest things?
    - jamesrom 14y ago
      I think he means the 11 hardest things actually.
      - alexkus 14y ago
        10 in ternary (which I think was his part of the joke)

mibbitier 14y ago

All they need to do is add a new "message" to say "y'know that message number 4029375 in the cache, yeah that ones deleted, ignore it". This is not hard.

natrius 14y ago
This arrogance is baffling. What makes you think you know enough about Facebook's infrastructure to make such a claim?
- mibbitier 14y ago
  huh? Infrastructure is totally and utterly irrelevant to the problem. I know enough about common sense to make such a claim. Just send a new message, exactly as you would post an original item/comment/etc, but have some special text/field in there that says "please ignore the previous message". The UI would then hide the previous message. eg COMMENT: {id:9374758, from:"mibbitier", data:"I hate you all!"} COMMENT: {id:9374759, from:"mibbitier", data:"*IGNORE_MESSAGE_IN_UI* 9374758"} Nothing whatsoever to do with infrastructure. Nothing to do with caches. Purely to do with the UI. Not rocket science. Granted, it's a poor way to do it, but it's better than nothing, and easier than trying to invalidate caches etc
  - mh- 14y ago
    I'm sure it's already rendered to a static presentation-level (HTML/template language du jour) form at that point. That wouldn't work.
    - mibbitier 14y ago
      Just put some more javascript in there to deal with it. I'm sure it's not the hardest problem in the world.
      - engtech 14y ago
        Great, you've hidden the message with javascript, but now it's still in view-source and in search results for bots. It's also still visible if someone is using noscript (actually, I have no idea if Facebook works with noscript, probably not). The solution you are suggestion doesn't solve the problem and injects more corner cases.
  - 14y ago