Are you seriously so dense that you can't figure out what you could use this for?
No, this is not useful for something that doesn't change over time, yes, this can be used in any case where content changes ever. The home page of your blog updating when a new article is posted? Check. Same for comments on said blog. Hacker news upvote counter changes? Sure.
I can't fathom how someone is so dumb to see "cache invalidation of web data" and jump to "can this be used for anything but status updates?". The article was already plenty generic and you're just being one dense motherfucker who happened to latch onto their chosen example and ignore the underlying point.
I don't mind OO / java, I like ruby, I'm hoping rust will be the new language worth using.
I strongly dislike Go for a variety of reasons, mostly dealing with its anti-OO sentiments actually. It has things like "for x := range myArr" but you can't implement that yourself because you actually can't implement either a single and multiple return or implement an iterator/range. The language is full of crap like that, where the programmer is treated like a baby who shouldn't have any power.
Similarly, the language has first class functions, but no functional constructs (map, etc). It doesn't have pattern matching or tuples so multiple-returns feel like a hack. Its error checking is atrocious.
It has no version control or package management worth shit; npm, bundler, etc, all have an idea of "I want something less than this version". In golang, it's worse than C even. They encourage go get, aka "pull from master, surely it won't break" or vendoring. At least in C, you have os package managers to do some of this and pkg-config.
Go is just a terribly designed language in almost every aspect in my opinion. It isn't functional and sucks at OO. It sucks at low level. It sucks at high level. It sucks at large project. It's okay until you need to implement your own type and realize you're a second class citizen.
Hopefully that made sense to you; thanks for asking nicely.
However, what I get even less is how every single person I've seen make a comment related to Go on an article unrelated to Go has been obviously dumb.
Seriously, what kind of idiot thinks this question or the one linked above makes sense? No, no one should do this table for Go. Go is not a dynamically typed language. Go does not have type coercion. Go's rules of equality are simple and obvious with the only exceptions being interfaces (equality of the underlying values) and nil (works as you'd expect).
Now please quit coding and never say the word Go again. It's a terrible language and you're a terrible person for commenting about it or using it.
I swear, I see dumber people using Go than PHP now-a-days; perhaps I should applaud the Go team for being the only group capable of making a language so terrible and yet so popular since PHP4.
Go learn a Haskell for greater good or, better yet, learn to delete your account and jump off a bridge so no-one has to suffer your terrible comments ever again.
No, this is not useful for something that doesn't change over time, yes, this can be used in any case where content changes ever. The home page of your blog updating when a new article is posted? Check. Same for comments on said blog. Hacker news upvote counter changes? Sure.
I can't fathom how someone is so dumb to see "cache invalidation of web data" and jump to "can this be used for anything but status updates?". The article was already plenty generic and you're just being one dense motherfucker who happened to latch onto their chosen example and ignore the underlying point.