3 ms·
Bad code is bad code, no matter which language. Languages won't save you from poor design choices. OOP is popular in large enterprise systems because it (purp
by tcbawo 8y ago
Bad code is bad code, no matter which language. Languages won't save you from poor design choices.
OOP is popular in large enterprise systems because it (purports to) promote encapsulation and abstraction, which allows many teams/people to interact. Organizations may like OOP because it helps reinforce their drive for independence and fiefdom (see Conway's law https://en.m.wikipedia.org/wiki/Conway%27s_law https://en.m.wikipedia.org/wiki/Conway%27s_law).
Whether it is the best paradigm, the most practical, 'just good enough', the wrong choice is anecdotal.
Also, in experience many companies would rather fail conventionally than succeed unconventionally.
- antidesitter 8y ago> Bad code is bad code, no matter which language. It’s easier to write bad code in some languages than others. > Languages won't save you from poor design choices. They do. They save you from entire classes of bugs, and make it less easy to shoot yourself in the foot. Do we need to have this conversation every time we talk about language design? Do you think the tool you use to achieve a task doesn’t matter?
- pka 8y ago> Do you think the tool you use to achieve a task doesn’t matter? I think many people do think that, with a twist; specifically, when presented with a higher level language they'd argue "it's just a tool", while a lower level language would be "the wrong tool for the job". I.e, for a hypothetical Ruby programmer, Haskell = "just a tool", C = "the wrong tool".