Functional, Procedural & Object-oriented Programming - An Overview

What's the difference between functional, procedural and object-oriented programming (OOP)? Let's take a closer look and build the same demo-app in three different versions!

----------

----------

• Follow @maxedapps and @academind_real on Twitter

See you in the videos!

----------

[lietuvisdarius]

Well done, best way to learn ANYTHING is to see alterntives! There is lots of videos on youtube teaching OOP or FP, but this video shows big picture, show difference. Thank you for that.

[javlonjuraev]

Take cooking a meal example.

OOP: organize your task as an interaction between different objects (cookware, ingredients, the cook)

Procedural: break down your task into steps and complete it one step at a time (just like following the recipe)

Functional: organize your task as actions you should take - cleaning, cutting, washing, frying etc.

[Am-ugnp]

I've heard a lot of people say that the object oriented is closest to how we think about the physical world and thus easiest to grasp, which is interesting to me, because it's been the hardest paradigm for me to grasp. I started out doing procedural, then functional, then object oriented. Even after learning OOP I still prefer functional, with just a little bit of object orientation. I like to organize my logic into functions and store data in struct objects

[AwestrikeFearofGods]

5:22 Procedural
12:01 Object-oriented
26:19 Functional

[madza]

From personal experience over years:
Procedural to OOP: why didn't i know this earlier?
OOP to Functional: this is the best thing ever!

[Videosuser]

I loved the way this class was structured comparing different programming paradigm styles.

[iamdhruvcool]

spent 2 days learning and reading about different paradigms and this one video cleared all my doubts, resources like these are rare. Keep up the good work guys !

[anonymoususer]

36:06: Throwing exceptions is also a side-effect. You could return an error value, here instead, to be handled by the caller. Often, this value is encoded as an either/or type with two cases: one for success and one for failure. The success case would be the constructed user object. The failure case could be a list of validation errors.

[ff-]

object-oriented style : 12:36
functional style : 25:49

[kemekenneth]

This is the best video I've watched on this paradigm topic. Showing all 3 in the same application just lets it sink. Thank you, boss.

[yahayaoyinkansola]

This is the best video I have found that has been able to make the whole concept behind OOP to make sense to me, thank you very much!!. To think this was 4 years ago

[analogylibrary]

A beauty of well organized explanation + clear on everything + good hands in programming style.
So you earned my subscription :)

[ademineshat]

Best part of the video : "The code is writing itself" :))

Thank you. Great Video

[Charles-syej]

So Happy I found this video, I think The Odin Project needs to link this video in their course because this made so many things so much more clear to me. I will definitely come back to watch this a few more times.

[houseandhobby]

The best video illustrating the differences. Your approach was the best out there that I could find. You did a great job of not picking sides too. Side effects. Not having them. I think that goal of fp is mistated by that paradigm. The only actual reason we program is in order *to achieve* side-effects. But let's do it black box-like, dry principle-wise, as cleanly as we can. That darn ui notification is needed. That file needs data and some fn somewhere needs to write to it. Functions of related functionalities belong in a code module or static class. And so we cross the fence and rightly put one leg into the OO side of the fence. Functions exist to provide some service so yes let's let them be specialized and flexible/reusable. I agree that we can and should merge fp with OO where "is-a" and "has-a" relationships exist. For goodness sake, we don't write code so that it cannot interact with the outside world. I've seen samples of fp code go too far in trying to not have side effects. Those examples are the new "spaghetti code" taking part of the blame off of "goto".

[LPArabia]

That was a really good introduction to functional programming in comparison with the more widely used oop and procedural approaches. Thank you Max!

[herseem]

Congratulations! FINALLY I found comparative examples of the exact same functionality, which seems to be missing from every other comparison between procedural and OOP that I've seen. And OOP is finally begining to make sense. But only beginning

[pascalbe]

Great video, Max. I really like this kind of content.
I'd like to add, that functional programming or (to be precise) pure functions make the code a lot easier to unit-test especially in comparison to the procedural style due to the lack of side effects. This is one of the biggest advantages in my eyes.

[donsurlylyte]

finally an intro that makes some sense of functional programming.good job. i can see now how it would be useful for larger structures

[calitts]

Finally a video that shows and compares the different paradigms with real code!