but socioeconomical. the oop paradigm has some strong points, as has any other, but it is quite unique in how it encourages classification in a broad sense, an approach that is much preferred in enterprise organization as it provides a (mostly imaginary but still appealing) degree of control over diversity. sort of bureaucratic mindset.
regarding the technical aspect, the hype for oop was pretty strong back in the day, and equally strong is the ongoing demonization, yet oop still thrives. both are equally baseless. my view is just get the right tool for the job and ignore all the fuss.
regarding the technical aspect, the hype for oop was pretty strong back in the day, and equally strong is the ongoing demonization, yet oop still thrives. both are equally baseless. my view is just get the right tool for the job and ignore all the fuss.
I tend to agree. It does some things well and some things poorly, but it took a lot of nasty trial and error to learn those lessons, and the lessons are still not codified enough to prevent the mistakes from repeating.
It works well in "mini domains" where the
If I set here and stare at nothing long enough, people might think
I'm an engineer working on something.
-- S.R. McElroy
i'd say the reason is not technical, (Score:2)
but socioeconomical. the oop paradigm has some strong points, as has any other, but it is quite unique in how it encourages classification in a broad sense, an approach that is much preferred in enterprise organization as it provides a (mostly imaginary but still appealing) degree of control over diversity. sort of bureaucratic mindset.
regarding the technical aspect, the hype for oop was pretty strong back in the day, and equally strong is the ongoing demonization, yet oop still thrives. both are equally baseless. my view is just get the right tool for the job and ignore all the fuss.
Re: (Score:1)
I tend to agree. It does some things well and some things poorly, but it took a lot of nasty trial and error to learn those lessons, and the lessons are still not codified enough to prevent the mistakes from repeating.
It works well in "mini domains" where the