7 ms·
Every once in a while I see this article, and every once in a while I fear that junior programmers are going to read it as if it is at all accurate. This is a
by x0hm 6y ago
Every once in a while I see this article, and every once in a while I fear that junior programmers are going to read it as if it is at all accurate.
This is a great article that represents the fundamental problem of OOP - that developers don't actually use it.
Instead, we have a lot of procedural programmers writing code that masquerades itself as "object oriented", when in reality it's imperative functional decomposition that we're calling OOP because we don't know any better.
- crimsonalucard5 6y agoI'm not sure what you're getting at here but JAVA code is really OO when compared to something like Go. If you consider java to not be OOP then it's a completely different story. If you consider java to not be OOP what would style would you call it? Is this what you're referring to with "imperative functional decomposition"?