I'm not here to pick a side. I'm sure all of us can be more friendly to each other.
However, I'm a bit curious about when you say
> Suggesting that someone pours over documentation (and laughably source code) to explain patterns (or a lack thereof) in a highly abstracted language is counter-productive.
Isn't that what documentation is for? To learn about whatever's being documented. What would you suggest would be the better way to convey this information?
For source code, I can see your point. Although in my experience source code has the benefit that you can be certain that it doesn't lie. It does exactly what it says. Sometimes this can be a really nice benefit when trying to figure out what's going on. Regardless of the language or environment you are in.
One thing not mentioned by other replies is that the discussion around the story of Last of Us got very polarized when the second game dropped. There was a very loud opposition from part of the fanbase to certain plot points, themes and other decisions made in the story. This made the people who still liked it get very defensive about it.
I see that same controversy continue with the discussion around the show which, typical to reddit, manifests as downvotes, reports and name calling (woke or bigots, depending on side)
However, I'm a bit curious about when you say
> Suggesting that someone pours over documentation (and laughably source code) to explain patterns (or a lack thereof) in a highly abstracted language is counter-productive.
Isn't that what documentation is for? To learn about whatever's being documented. What would you suggest would be the better way to convey this information?
For source code, I can see your point. Although in my experience source code has the benefit that you can be certain that it doesn't lie. It does exactly what it says. Sometimes this can be a really nice benefit when trying to figure out what's going on. Regardless of the language or environment you are in.