4 ms·
I'm glad to be part of the anti-OOP backlash that's become trendy in recent years. Unrestrained OOPness leads to the kinds of "Java-isms" we all know and love.
by phendrenad2 6y ago
I'm glad to be part of the anti-OOP backlash that's become trendy in recent years. Unrestrained OOPness leads to the kinds of "Java-isms" we all know and love. MyApp::Core::BeanStringFactoryProviderImpl. Stuff like that.
However, if you turn your back on OOP entirely, where does that leave you? You have to go down the functional programming route.
FP has it's own problems. Ever see a large FP-style JS program? It resembles procedural code. Functions strewn around the codebase with no hierarchy or compartmentalization. Anything can (and will) call anything. You pipe data along from function to function, but you quickly find that the chunks of data that you're sending keep... growing... because you can't keep the entire codebase in your head, and you can't remember that variable X is equivalent to Y in all cases, so you just pass Y along also.