Object Oriented Programming has been the standard for the industry for decades now. However, as implemented in the various object oriented programming languages, it's more complex and difficult to manipulate than commonly understood. Having worked with a number of object oriented programming languages and non-OOP languages, I thought I'd state the case for avoiding
Ever noticed that Java has no header files? Instead, Java uses one file to store each public class and its functions.
Why would they require each class to have its own file? It's a question of simplicity for the Java designers. The Java precompiler (as it were) builds class symbols using the file names, which
In languages like Java, we have a standardized error-handling paradigm in the try-catch expression. Effectively, this hands all error-handling off to the computer, which monitors all code in the try loop for any and every kind of possible error. While we are able to restrict the range of errors in many cases, the fact
How many times have I seen this pattern in object oriented code?
All members of the class are private
All members can be accessed with accessor functions
All members can be changed with modifier functions
I hate to break it to y'all, but that's just a struct. The only thing you've done is add a hundred lines
Most modern languages are designed around the object oriented design principles. They contain syntactic elements that codify and require these principles for code implementation.
Unfortunately, as is common with modern minds, we leave everything up to the computer. This results in a gigantic block of generalities, the result of which is slow code that is
I've spent a number of years refining my arguments against modern object oriented programming languages.