▲ 342 ▼ What are your programming hot takes? (lemmy.ml) submitted 3 years ago by 257m@lemmy.ml to c/programming@programming.dev 894 comments fedilink hide all child comments
[–] ahmed@discuss.tchncs.de 32 points 3 years ago (7 children) Oop is overrated I never can understand classes permalink fedilink source hideshow 14 child comments replies: [–] karlhungus@lemmy.ca 13 points 3 years ago (1 child) Wow, nice hot take! I find the concept super intuitive, like a blueprint or a mold. permalink fedilink source parent hideshow 2 child comments replies: [–] spartanatreyu@programming.dev 1 point 3 years ago (2 children) It's intuitive until you realise that not everything fits in a single inheritance hierarchy. This gives a good example: https://www.youtube.com/watch?v=wfMtDGfHWpA permalink fedilink source parent hideshow 4 child comments replies: [–] PipedLinkBot@feddit.rocks [B] 2 points 3 years ago Here is an alternative Piped link(s): https://piped.video/watch?v=wfMtDGfHWpA Piped is a privacy-respecting open-source alternative frontend to YouTube. I'm open-source, check me out at GitHub. permalink fedilink source parent [–] karlhungus@lemmy.ca 1 point 3 years ago (1 child) I think of OOP as encapsulation, abstraction, and polymorphism primarily. Inheritance is definitely taught as part of it, but it seems like most people have found that to be the least used part of it. It seems like you understand oop, but find it overrated, from your post it sounded like you didn't understand it -- but maybe you meant you didn't understand it's popularity. permalink fedilink source parent hideshow 2 child comments replies: [–] spartanatreyu@programming.dev 1 point 3 years ago I absolutely understand OOP, its explosion took over everything that took a long time to recover from. The problem with OOP is that it's pushed as a cure-all both by teachers who do not the problems it solves and also do not understand its own limitations. In almost every situation where OOP makes sense, something else makes more sense to use. permalink fedilink source parent [–] SoBoredAtWork@lemmy.world 13 points 3 years ago (1 child) So... "thing I don't understand is overrated"? permalink fedilink source parent hideshow 2 child comments replies: [–] reverendsteveii@lemm.ee 4 points 3 years ago I understand OOP. I like it. I also took my first coding classes in the late 90s and we were taught OOP as though it was the last coding paradigm that would ever be needed. It really set me back because I didn't even understand the principles of the functional paradigm until I was already at my first coding gig permalink fedilink source parent [–] finestnothing@lemmy.world 7 points 3 years ago I may not love oop, but it is extremely useful in the cases that you should use it permalink fedilink source parent [–] Double_A@discuss.tchncs.de 3 points 3 years ago Often it's just a container for a bunch of related functions and common state variables for all those functions. Rarely are classes actually used in the OOP way, where you then create many instances of that class... permalink fedilink source parent [–] 257m@lemmy.ml [S] 3 points 3 years ago (1 child) OOP isn't classes though but I get what your saying. permalink fedilink source parent hideshow 2 child comments replies: [–] BatmanAoD@programming.dev 8 points 3 years ago OOP is classes, and their accompanying language features (primarily inheritance) and design patterns (e.g. factories). permalink fedilink source parent [–] MajorHavoc@lemmy.world 2 points 3 years ago Agreed. Inheritance, specifically, is a huge code smell. When inheritance is acting as a quick way to implement an interface, it's lovely. When an object is acting as a fancy dictionary, it's lovely. When a class has more than one parent in it's chain of inheritance (upwards or sideways), that's a code smell. It specifically tells us that the developers are trying to manage program state (variables and data) that simply should have been refactored out (or have drifted very far from the code they're actually needed by). permalink fedilink source parent [+] AureumTempus@lemmy.world 1 point 3 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent
[–] karlhungus@lemmy.ca 13 points 3 years ago (1 child) Wow, nice hot take! I find the concept super intuitive, like a blueprint or a mold. permalink fedilink source parent hideshow 2 child comments replies: [–] spartanatreyu@programming.dev 1 point 3 years ago (2 children) It's intuitive until you realise that not everything fits in a single inheritance hierarchy. This gives a good example: https://www.youtube.com/watch?v=wfMtDGfHWpA permalink fedilink source parent hideshow 4 child comments replies: [–] PipedLinkBot@feddit.rocks [B] 2 points 3 years ago Here is an alternative Piped link(s): https://piped.video/watch?v=wfMtDGfHWpA Piped is a privacy-respecting open-source alternative frontend to YouTube. I'm open-source, check me out at GitHub. permalink fedilink source parent [–] karlhungus@lemmy.ca 1 point 3 years ago (1 child) I think of OOP as encapsulation, abstraction, and polymorphism primarily. Inheritance is definitely taught as part of it, but it seems like most people have found that to be the least used part of it. It seems like you understand oop, but find it overrated, from your post it sounded like you didn't understand it -- but maybe you meant you didn't understand it's popularity. permalink fedilink source parent hideshow 2 child comments replies: [–] spartanatreyu@programming.dev 1 point 3 years ago I absolutely understand OOP, its explosion took over everything that took a long time to recover from. The problem with OOP is that it's pushed as a cure-all both by teachers who do not the problems it solves and also do not understand its own limitations. In almost every situation where OOP makes sense, something else makes more sense to use. permalink fedilink source parent
[–] spartanatreyu@programming.dev 1 point 3 years ago (2 children) It's intuitive until you realise that not everything fits in a single inheritance hierarchy. This gives a good example: https://www.youtube.com/watch?v=wfMtDGfHWpA permalink fedilink source parent hideshow 4 child comments replies: [–] PipedLinkBot@feddit.rocks [B] 2 points 3 years ago Here is an alternative Piped link(s): https://piped.video/watch?v=wfMtDGfHWpA Piped is a privacy-respecting open-source alternative frontend to YouTube. I'm open-source, check me out at GitHub. permalink fedilink source parent [–] karlhungus@lemmy.ca 1 point 3 years ago (1 child) I think of OOP as encapsulation, abstraction, and polymorphism primarily. Inheritance is definitely taught as part of it, but it seems like most people have found that to be the least used part of it. It seems like you understand oop, but find it overrated, from your post it sounded like you didn't understand it -- but maybe you meant you didn't understand it's popularity. permalink fedilink source parent hideshow 2 child comments replies: [–] spartanatreyu@programming.dev 1 point 3 years ago I absolutely understand OOP, its explosion took over everything that took a long time to recover from. The problem with OOP is that it's pushed as a cure-all both by teachers who do not the problems it solves and also do not understand its own limitations. In almost every situation where OOP makes sense, something else makes more sense to use. permalink fedilink source parent
[–] PipedLinkBot@feddit.rocks [B] 2 points 3 years ago Here is an alternative Piped link(s): https://piped.video/watch?v=wfMtDGfHWpA Piped is a privacy-respecting open-source alternative frontend to YouTube. I'm open-source, check me out at GitHub. permalink fedilink source parent
[–] karlhungus@lemmy.ca 1 point 3 years ago (1 child) I think of OOP as encapsulation, abstraction, and polymorphism primarily. Inheritance is definitely taught as part of it, but it seems like most people have found that to be the least used part of it. It seems like you understand oop, but find it overrated, from your post it sounded like you didn't understand it -- but maybe you meant you didn't understand it's popularity. permalink fedilink source parent hideshow 2 child comments replies: [–] spartanatreyu@programming.dev 1 point 3 years ago I absolutely understand OOP, its explosion took over everything that took a long time to recover from. The problem with OOP is that it's pushed as a cure-all both by teachers who do not the problems it solves and also do not understand its own limitations. In almost every situation where OOP makes sense, something else makes more sense to use. permalink fedilink source parent
[–] spartanatreyu@programming.dev 1 point 3 years ago I absolutely understand OOP, its explosion took over everything that took a long time to recover from. The problem with OOP is that it's pushed as a cure-all both by teachers who do not the problems it solves and also do not understand its own limitations. In almost every situation where OOP makes sense, something else makes more sense to use. permalink fedilink source parent
[–] SoBoredAtWork@lemmy.world 13 points 3 years ago (1 child) So... "thing I don't understand is overrated"? permalink fedilink source parent hideshow 2 child comments replies: [–] reverendsteveii@lemm.ee 4 points 3 years ago I understand OOP. I like it. I also took my first coding classes in the late 90s and we were taught OOP as though it was the last coding paradigm that would ever be needed. It really set me back because I didn't even understand the principles of the functional paradigm until I was already at my first coding gig permalink fedilink source parent
[–] reverendsteveii@lemm.ee 4 points 3 years ago I understand OOP. I like it. I also took my first coding classes in the late 90s and we were taught OOP as though it was the last coding paradigm that would ever be needed. It really set me back because I didn't even understand the principles of the functional paradigm until I was already at my first coding gig permalink fedilink source parent
[–] finestnothing@lemmy.world 7 points 3 years ago I may not love oop, but it is extremely useful in the cases that you should use it permalink fedilink source parent
[–] Double_A@discuss.tchncs.de 3 points 3 years ago Often it's just a container for a bunch of related functions and common state variables for all those functions. Rarely are classes actually used in the OOP way, where you then create many instances of that class... permalink fedilink source parent
[–] 257m@lemmy.ml [S] 3 points 3 years ago (1 child) OOP isn't classes though but I get what your saying. permalink fedilink source parent hideshow 2 child comments replies: [–] BatmanAoD@programming.dev 8 points 3 years ago OOP is classes, and their accompanying language features (primarily inheritance) and design patterns (e.g. factories). permalink fedilink source parent
[–] BatmanAoD@programming.dev 8 points 3 years ago OOP is classes, and their accompanying language features (primarily inheritance) and design patterns (e.g. factories). permalink fedilink source parent
[–] MajorHavoc@lemmy.world 2 points 3 years ago Agreed. Inheritance, specifically, is a huge code smell. When inheritance is acting as a quick way to implement an interface, it's lovely. When an object is acting as a fancy dictionary, it's lovely. When a class has more than one parent in it's chain of inheritance (upwards or sideways), that's a code smell. It specifically tells us that the developers are trying to manage program state (variables and data) that simply should have been refactored out (or have drifted very far from the code they're actually needed by). permalink fedilink source parent
[+] AureumTempus@lemmy.world 1 point 3 years ago* (last edited 2 years ago) [deleted] permalink fedilink source parent