While the concept has it’s uses as a tool, the fallacy that OOP advocates fall into is overusing it.
I’ve seen many people completely swear off of using scripts, which is absolutely ridiculous. While you may use some tools more than others, swearing off an entire code structure for no reason is ridiculous.
Say there’s a module of code you need to write that has hundres if not thousands of variables that come into play in combinations that would be extremely difficult to organize as functions. You’re then stuck with passing all those as inputs and outputs between functions.
Sure, you could organize all those variables as a giant array and pass them around as one big block, but at that point you’re just emulating the shared workspace that you get with scripts, and you’d just be better off working with scripts from the start.
The issue with OOP is that it completely ignores this reality and insists that nobody should ever need a script, and if they think they do then they just aren’t clever enough.
Well you’re not wrong, but man, you’re hating the screwdriver because you work in a bolt factory.
Use the took that best suits your problem, right?
Also: what’s that code that has thousands of variables that cannot be organised? If it isn’t just an example for the sake of an example, I’m genuinely curious! And how does scripts “fix” that?
Also: I have always hated java for their overuse of OOP, but also restricting its use, wtf.
Also: I love a straightforward script, on linux at least!
Why? I find it quite useful.
While the concept has it’s uses as a tool, the fallacy that OOP advocates fall into is overusing it.
I’ve seen many people completely swear off of using scripts, which is absolutely ridiculous. While you may use some tools more than others, swearing off an entire code structure for no reason is ridiculous.
Say there’s a module of code you need to write that has hundres if not thousands of variables that come into play in combinations that would be extremely difficult to organize as functions. You’re then stuck with passing all those as inputs and outputs between functions.
Sure, you could organize all those variables as a giant array and pass them around as one big block, but at that point you’re just emulating the shared workspace that you get with scripts, and you’d just be better off working with scripts from the start.
The issue with OOP is that it completely ignores this reality and insists that nobody should ever need a script, and if they think they do then they just aren’t clever enough.
Well you’re not wrong, but man, you’re hating the screwdriver because you work in a bolt factory.
Use the took that best suits your problem, right?
Also: what’s that code that has thousands of variables that cannot be organised? If it isn’t just an example for the sake of an example, I’m genuinely curious! And how does scripts “fix” that?
Also: I have always hated java for their overuse of OOP, but also restricting its use, wtf.
Also: I love a straightforward script, on linux at least!
That’s because you haven’t unlearned it yet