Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on OO in Python is mostly pointless. Parent comment
There is no such paradigm, including and specially OO.
In fact, your example clearly illustrates the perils of blaming the tools for problems caused by incompetence.
I mean, how many decades have passed since "composition over inheritance" has been taught like a mantra in every OO programming 101 course?
And still the best OO example you could manage to come up wit is a blatant error that would lead you to fail a OO programming 101 course?
I'll restate the obvious: the reason why bad code is bad is not because it's OO, it's because it's bad code.
And here you are, trying to pass blatantly bad code as somehow an OO problem?
There are no comments on this comment yet.
There is no such paradigm, including and specially OO.
In fact, your example clearly illustrates the perils of blaming the tools for problems caused by incompetence.
I mean, how many decades have passed since "composition over inheritance" has been taught like a mantra in every OO programming 101 course?
And still the best OO example you could manage to come up wit is a blatant error that would lead you to fail a OO programming 101 course?
I'll restate the obvious: the reason why bad code is bad is not because it's OO, it's because it's bad code.
And here you are, trying to pass blatantly bad code as somehow an OO problem?