A whole article and no code examples. Fail.
I think OOP people should be aware that there is significant backlash against OOP among smart people who are very familiar with the paradigm and they should take the time to understand why.
The division is real and given the invention of languages like GO and RUST that do not have classes I would think really hard about the topic.
If you are using GO like you use OO, you've missed the entire point.
You literally said go removed virtual methods. This is not what pike is talking about. Pike is talking about putting a function onto your struct. This is legal in go as functions are first class but rob is saying it should be done sparingly because data and behavior need to be distinct concepts.
It is not me who failed to parse your writing, but you who failed to understand pike and my comment.
Say if you practiced procedural programming in a very heavy way and typed functional programming in a major way along with OOP then you would have a better picture.
If you practiced OOP exclusively for the majority of your career I would argue your view point is flawed and biased. Over the years, as a programmer with a lot of heavy experience in all of the paradigms mentioned above, I have found that OOP is in fact not an apples and oranges comparison to other programming styles but is in fact a highly flawed paradigm.