Re:C for All
by crimsonalucard on Saturday March 24, 2018 @10:48AM
(#16666826)
Mantras decrying a built in feature of OO are just flaws within the paradigm.
I don't think it's trendy if newer next generation languages like go rust and nim avoid OO. These experts who design languages know something.
Re:C for All
by seabrookmx on Saturday March 24, 2018 @01:05PM
(#16667573)
I never said it was trendy for languages to not include class-based OO (see most functional languages), I said it was trendy for people to bash it.
Like I said, I regularly write Go and don't have trouble with it's interfaces and duck typing.
> These experts who design languages know something
What about the experts who bolted classes onto ECMAScript? I don't think it's black and white. It's like the static vs. dynamic debate.. there is pros and cons of each approach.
Re:C for All
by crimsonalucard on Saturday March 24, 2018 @03:08PM
(#16668271)
They didn't bolt classes onto es6. It's more like syntactical sugar over existing features.
I think among many language designers starting a whole new language, the issue is indeed black and white.
OO can _definitely_ be misused and I think the disconnect is that the traditional abuses of OO (deep class hierarchies, fragile base classes, etc) are associated to "oldschool" Java and C++ codebases. But if developers followed the "composition over inheritance" mantra back then, maybe this complaint wouldn't be so prevalent.
I pretty fluidly move between Typescript/C#/GoLang and after the initial hump in GoLang, I find I don't have much preference. Some code feels more clunky without "traditional" OO and some feels better. I've yet to really dive into traits in Rust but I'm guessing I'll feel the same way when I get around to it.