2 ms·
>You can see what is happening in a piece of code just by looking at the local context ^ This. A thousand times this. When I read this article, all I could th
by yomly 7y ago
>You can see what is happening in a piece of code just by looking at the local context
^ This. A thousand times this.
When I read this article, all I could think was _this_ is what object oriented code is meant to be about, aka message passing.
I have been working on a Rails codebase and it's an absolute nightmare - without knowing everything all at once you can come to a tiny class that has a bunch of identifiers set via inheritance or somehow used via inflection. It's completely mad.
Not meaning to start a flame-war but it confuses me how OO went from a simple idea of encapsulated "objects" having well defined interfaces to this crazy spaghetti mess of inheritance etc.
That said, bad code is bad code and you can ship a ball of mud in anything...