Re:The Big OOPs: Anatomy of a Thirty-Five Year Mistake
by lisbbb on Wednesday July 23, 2025 @11:55PM
(#44666741)
OOP is not shoved down your throat with Python, though. With Python, I can choose what taxonomies deserve an OOP treatment and which do not. Spoiler: Almost nothing is a taxonomy of any remarkable nature.
Re:The Big OOPs: Anatomy of a Thirty-Five Year Mistake
by JohnMakin on Thursday July 24, 2025 @12:59AM
(#44667110)
you also can get away with completely ignoring the underlying oop semantics in tons of cases whereas java and similar languages dont give you that option
Re:The Big OOPs: Anatomy of a Thirty-Five Year Mistake
by fc417fc802 on Wednesday July 23, 2025 @11:39PM
(#44666643)
If I call something a function does that mean I'm "doing functional programming" any time I use it?
I use both C++ and Python but I wouldn't describe any of what I write as "object oriented".
Re:The Big OOPs: Anatomy of a Thirty-Five Year Mistake
by lisbbb on Wednesday July 23, 2025 @11:55PM
(#44666742)
No. Functional programming is quite a bit more involved than just writing "functions"--it is taking advantage of the fact that functions are first-class "objects" that can be passed as arguments to other functions, which allows for a far more intuitive and flexible form of programming. But FP is even more than that.
Do you just mean that Python lets you write functions not as part of a class? Because yeah there's the public static void main meme but static functions attached to a class is basically equivalent to Python free functions being attached to a module object.