3 ms·
> he's against the extreme "everything is an object" version of OOP I totally agree with you. I think he focuses on this style because it's generally what's ta
by codemonkey-zeta 4y ago
> he's against the extreme "everything is an object" version of OOP
I totally agree with you. I think he focuses on this style because it's generally what's taught in Universities, and he also has tons of tutorials geared towards students. So he's exposing his audience to the idea that some OOP principles are good, but overly adhering to the paradigm (in the way that would get you a 100% grade in an OOP class in college) is actually a bad way to program in general.
- magicalhippo 4y agoThat's a fair point, and as I mentioned I do agree with his conclusion. Being self-taught, I was already a proficient programmer in Delphi and C++ by the time I went to University. So to me OOP has always been "OOP when you need it". Though now that you mention it, even by the time I started University I had a profound dislike for Java's "OO all the things" approach. It has not subsided...