Why was OOP Invented? 

Stefan, you communicate with us like a wise father or uncle would. I never notice any inflammatory, condescending remarks or undertones in your videos, or trying to put someone else down. This world needs more of that. Very positive, edifying channel!

Ruby is an almost pure object oriented language. Thought that would be good to mention this on this chanel

I've been told that the main purpose of inheritance is not to "reuse code", rather than that it's purpose is to allow polymorphism. Which means that you can have multiple classes that inherit from a more generic superclass, all objects of these classes could then be used in a code that was programmed to be compatible with the superclass.

People talk about OOP as if inheritance is all there is to it or is the most important aspect of it when there are so many other things that give it its identity.

When I was first starting out I admit I'm one of those people who overused inheritance because every book and tutorial made it sound like the best thing every invented. As I started getting into more complex systems, I saw the weaknesses that you mentioned. You can end up with an unmaintainable system if you blindly use inheritance for the sake of reusability. I think the thing to remember is that inheritance does have its place. Obvious example: if you're writing any Java, you're automatically using inheritance because everything in Java inherits from Object by design. Also, I've used inheritance sparingly in the data layer where the app is interacting with the database. Basically the kind of logic that all the data classes will be using, like setting up the connection, closing connection, etc. That's one case where it makes sense.

i would say that a mix of procedural and oop is the best just my opinion do. when you have lots of simllar stuff use oop. when you have function (not methods) that are used every where or the main function use procedural. doing pure procedural right now its really fun compered to oop.

What is your opinion on functional languages like F# (advantages disadvantages vs OOP C#)

I agree about excessive use of inheritance. I worked with .NET and C# for many years and everything inherits ultimately from Object but the number of classes in the chain is often ridiculous. The idea of OOP actually goes back to the 1950s when it was simulated in non OOP languages, FORTRAN I think. I actually like the Python paradigm where OOP is optional, and even if you do use it it's a fairly liberal version of OOP whereas some languages (cough C# cough) are so paranoid they almost make you feel like a criminal. "How dare you try to use that method, it's PRIVATE." Has anybody noticed that most of the mainstream OOP languages were created by Scandinavians? Simula, C++, C#?

Which is the video describing using interfaces instead of inheritance? I can’t find it on your channel. Thanks.

I took a class on C# this year and it’s the first programming class I’ve ever taken and it wasn’t that hard to learn. (I only know the basics though)

I don't know why, but I love your OOP and inheritance vlogs))

If you think structures and procedural coding causes spaghetti code, wait until you start using OOP. I think the biggest problem with OOP are class libraries that try to do too much. Any particular library of the past - going back to Think Class Libraries ( TCL ) - from 1987, through MFC, through CodeWarrior, through Swing, through all kinds of other things - they just made them too generic and code bloat that makes the Hindenburg look like a drug store mylar balloon.

I've been told by people who earn twice as much money as me that polymorphism would be "exactly the OOP thing we all hate", and why Go's interfaces are so much better than whatever Java does. Everything comes full circle. First OOP was great and advocated for by smart people, then dumb people misunderstood it, then smart people critizised it, then it survived and now dumb people continue to "critizise" it.

@Stefan, can you please comment Fred Brook's quote: "What one programmer can do in one month, two programmers can do in two months"

I'm now using SASS. Now I get why its beneficial. Maintainability!

so does it mean that it is less secured / if its easily breakable as you mentioned relative to other inheritance-free style of programming ? your input is highly appreciated best

OOP was actually invented to confuse the new programmers. Lol

I don't think of inheritance as code reuse. It's subtyping, and if code is reused, it is a lovely side-effect. Like, a book can be a physical book or an eBook.

you did not answer the question... you can write perfectly clean code with procedural language... OOP has todo with compiling external libs

There are many environments we work in that are nothing but structures of objects. Dot net programming for example. Inheritance is integral to developing in that environment.

Is it REALLY better organized? I dunno, man... Modularity you speak of in Classes could be emulated pretty well with opaque pointers in C. You do not need "classes" to break up your programs into reasonably sized chunks.

Polymorphism is by far the most important feature of OOP. But you are not the first one to get it wrong. Inheritance as it is, is like ... whatever ... sometimes useful. Encapsulation might be the other most important part. Also, I duplicate code all the time. It is mandatory across context boundaries.

In OOP inheritance is the first priority way to do things. It's one of the major ideas of OOP. If you can't for some reason get it, just don't use OOP language, but also don't try to downplay inheritance just because you don't understand it. "Avoid inheritance" is extremely bad advice to give and can in theory hold back people who try to learn OOP.

was that "Bob's your uncle"? ha ha

Is OOPs the plural?

Can I use Symfony framework for small or medium size projects?

Like all things in this world, everything in moderation and the application of the best tool for the job. The very basics of OOP, inheritance, encapsulation and polymorphism are all you really need. Everything else is just trendy bullshit, as the overuse of patterns and use of ORM's have shown. A well written program, in a language that allows it, will have elements of procedural (even modular), OOP and functional dotted through out. PHP is great for this. In the MVC paradigm, procedural code would normally dominate the controller scripts and the model will consist of one abstract class and many classes that derive the basic functionality from that, especially when writing database applications. Design the database first and add the business rules in the model on a per table basis. Functional elements are extremely handy for filtering, mapping and reducing data whilst keeping the original lists (arrays) intact. The view will invariably be HTML templates that accept data from the model. Things such as games programming are another kettle of fish entirely and I have no interest in those particularly. My knowledge of physics and calculus is not strong enough.

hey stefan, you always say "learning 20 mins a day 5 days a week is better than learning 100 minutes a day once a week" but what about learning and practicing 3-5 hours a day? do you think that's a healthy amount of time per day and would an average brain retain the knowledge at this pace? provided that I keep going back to the basics often to get some refreshers as i inevitably forget some stuff

It's just a way of categorizing code. Just like namespaces or filesystem folders.

and with OO you can get into Macarrones code

When it comes to cheese and bacon; why not choose both?

Nope. You can search online. OOP originally was for message handling between computers. The guy wanted to mimic networks by having objects send messages to other objects.

People confuse benefits of languages like Java with benefits of OOP. No, code in Pascal or C is spaghetti not because its lack of OOP. There are no garbage collection, no built-in data types besides array of bytes, no rich libraries, no stacktraces when program crashes. You don't understand that there was a great problem even to return something from function bigger than single number. It also was different kind of problems and different IDEs and hardware... There was ton things that made life easier and code prettier. Not OOP. Just try write code today in modern language without OOP. It would much easier, because you will not face any problem you have told will be without OOP.

how good is a Cs degree to get into AI

More of these nuggets uncle Stef......i like.

Who's Down with OOP!?

i dont think i wrote a single interface or inheritance outside of educational environment

We all made the mistake of inheriting everything creating a hierarchy mess then we learned about object composition.

y’all don’t stay for too long he gotta go to lunch

Inheritance for interfaces only!

Great explanation! Could you link us the Inheritance video?

Cmon man... cheese all day everyday.

Did you have a wedge of bacon cheese for lunch?

GOTO

Looking healthy your face looks much leaner

Packaging..... The real world is so overloaded with wasteful packaging the virtual brainz followed suit..... How many layers of packaging before we even dig out the code... and then we get to the guts and find loads more boxes full of boxes full of different sweets in different wrappers.... Truly horrible in so many ways...

OOPsie daisy

Watch it on 4x

try to scale a project without OOP , you can not. try to make a small project with OOP you can but is overkill.

Sksksksksksksks and i oop

The meme

OOP is an overly abstracted mess.....

Yeah I mean nobody needs it lets just put everything in one main function😂😂

tell me a single feature of any programming language that is native to OO that hasn't been discredited or discarded or replaced by something better? NONE!!! ALL OO is history and that is why you have none of those features in Rust. Rust is safe and is 99.99% the performance of C/C++ so we are paying safety with 0.01% of performance, is worth it.

Oop was invented because people got sick of functional xD

this video is utterly devoid of content