I used to hate OOP and now use is quite often. OOP does have the power to simplify coding through abstraction. An ORM like SqlAlchemy is a good example of OOP that simplifies coding, where your database objects magically become objects in your code.
However, today OOP is not as big of a problem.
Frameworks.. picking a framework, learning the framework, dealing with poor documentation and bugs, then learning a new framework that does the exact same thing when another programmer decides to abandon the current framework.
Or, you could just write your own framework and join the fray, maybe fork and existing framework.:)
I don't hate OOP but I recognize that is is not at all what it was original sold to be.
Frameworks are definitely my biggest nemysis today because they always constrain what you can do and how you solve problems. However, conventional OOP was also a bad idea in and of itself. Exactly zero of it's claims came true, in practice. It's now much harder to write and maintain software than it used to be...
I see JavaScript and Rust as saviors. JavaScript's prototype OO model is far more efficient. Rust avoid co
I absolutely agree with this. The clever IT chaps at work used what looked like a convenient framework to make a stock control system. But then there were things we needed to do that the framework would not let us do. And an innocent amendment could have unexpected consequences.
One example of frameworks I came across is related to the open source Asterix private telephone system. This uses loads of configuration files, written in the most obscure syntax. I am talking cat walked on the keyboard stuff. So som
ORM's are great when they reduce grunt-work but can be tricky to troubleshoot when they don't work as intended. Magic is a two-edged sword.
I'd rather have something in-between: something that simplifies 90% of grunt work but not with so many layers that it's not dissect-able without years of experience with it. I want an assistant, not a Cohen-style "fixer".
If I set here and stare at nothing long enough, people might think
I'm an engineer working on something.
-- S.R. McElroy
It's the FRAMEWORKS people hate today, not OOP (Score:4, Interesting)
I used to hate OOP and now use is quite often. OOP does have the power to simplify coding through abstraction.
An ORM like SqlAlchemy is a good example of OOP that simplifies coding, where your database objects magically become objects in your code.
However, today OOP is not as big of a problem.
Frameworks .. picking a framework, learning the framework, dealing with poor documentation and bugs, then learning a new framework that does the exact same thing when another programmer decides to abandon the current framework.
Or, you could just write your own framework and join the fray, maybe fork and existing framework. :)
Re: (Score:3)
I don't hate OOP but I recognize that is is not at all what it was original sold to be.
Frameworks are definitely my biggest nemysis today because they always constrain what you can do and how you solve problems. However, conventional OOP was also a bad idea in and of itself. Exactly zero of it's claims came true, in practice. It's now much harder to write and maintain software than it used to be...
I see JavaScript and Rust as saviors. JavaScript's prototype OO model is far more efficient. Rust avoid co
Re: (Score:1)
I absolutely agree with this. The clever IT chaps at work used what looked like a convenient framework to make a stock control system. But then there were things we needed to do that the framework would not let us do. And an innocent amendment could have unexpected consequences.
One example of frameworks I came across is related to the open source Asterix private telephone system. This uses loads of configuration files, written in the most obscure syntax. I am talking cat walked on the keyboard stuff. So som
Re: (Score:1)
ORM's are great when they reduce grunt-work but can be tricky to troubleshoot when they don't work as intended. Magic is a two-edged sword.
I'd rather have something in-between: something that simplifies 90% of grunt work but not with so many layers that it's not dissect-able without years of experience with it. I want an assistant, not a Cohen-style "fixer".