Correction: it doesn’t hide functionality; it hides implementation. Functionality is public, whereas implementation is private.

Jeez thank you so much. Clear and straight to the point.

It helps me so much, thanks man... think understand abstraction as all code/form to resolve a project that's hidden form the final user, who send the enter and get back a result for this. That part are called Abstration because it changes from each person who create a method to resolve the project... Hope be right, and help someone...

Saw 5 videos on this topic and this is the best explanation lol

very simple and easy to understand explanation thank you

what would be the difference between abstraction and encapsulation? seems both are intending to hide the actual implementation

Great video , loved it

abstract class can't create object but video example create a phone object please explain ?

Thank you ❤

The future of Binance: an exclusive interview with the CEO

great video

broooo you really cleared my mind thank you

Just a correction and modification of some concepts ------- Abstraction is not that concept of showing or providing only the important things and hiding all unnecessary or complex details from the user (the programmer), as everyone thinks You kindly explained that Abstraction is to provide only what the user can get, in short, to provide only the Important points in the classes that will be instanciated using an Object, and this is unfortunately wrong.... And if it was actually in this sense, the name would have been Only-Important-members or Hidding Data and so on... --------- In short, your concept is part of the definition of Encapsulation and not Abstraction, and it is very close to the concept of inheritance more than Encapsulation --------- Linguistically: Abstraction means intangible or imaginary or virtual or the opposite of Concrete which means tangible, real or active --------- Programmatically: It specifically means the Class and the Interface (interface is not available in all programming languages). The important thing is the Class in itself. And any Class in OOP is considered as a Template, Model, or Map of something in Reality. That thing may be real or imaginary, and as it may be tangible or intangible, it does not matter the Projection and how .... but it matters The Classes that will Ultimately Express an Entity, Component, or Object that we will deal with later.... -------- So Abstraction in OOP will be like that: Modeling the Real World. and No more than this Definition .. -------- There are also inactive, intangible, or Abstract Classes that we call them Class Model, and they are somewhat similar to the Interface. This type has a directive of type Abstract and it does not accept instanciate with Objects, that is, it has no Objects to represent it (No Instances). And her task is Only to make a Model or Template for her children's that inherited from and finally can share members from base Abstract Classe. And this technique is also within the definition of the corner Abstraction And my concept here is in modeling and not in the role of the abstract class (because its role in terms of providing only what the sons classes can share as members and this is a part from the corner of inheritance) finally : Abstract classes is an Abstract Model for a Concrete classes Where this concrete will be a Models for some objects in our Real World... -------- Interfaces are also a Model or Abstract that Classes use them in-order to benefit from those members in that Interface.. So, Abstraction OOP is only about these three things in C Sharp, Java and Delphi and maybe C++ builder(because all of them have Interface as far as I know now) ------ As for the definition that you explained in the video, it is related to Encapsulation and Inheritance rules and not Abstraction at All .. ----- Abstraction is the first Step Rule of OOP Pillars wich is the Classes and Interfaces ... Abstraction is not more than a Modelling ... ----- And thank you for your understanding ...

😂 that ending #dirtysecret

You are Dev! Damn right you are!!!!

You are a good teacher

this video is very useful to me

very nice

Thankyou

your way of explaining the stuff is very nice I will take some of your style and use in my coding channel if you don't mind

best explanation on YT

Man it's too tough to hide it ima do it I WAS NEVER A GOOD PROGRAMMER IN THE FIRST PLACE phew that felt nice

This is a way of seeing the world. Use abstractions irl!

thanks you so much

great vids - new sub

but what is meaning for this sentence "object are python abstraction for data"...?

so Abstraction is a blackbox, where you apply input and get output without caring about what’s inside!

Thank you so much, oh my god.

Why cant my teacher be this clear? Thanks!

So is abstraction the divide between Front-end development and Back-end?

Thank you for the clear example, I got sick of the car example.

👍

isnt this encapsulation not abstraction?

IMHO You told us about encapsulation. I expected that you tell a story why in Java we call Interfaces an Abstract classes "ABSTRACTION"

LOL no need to attack me like that, TWICE.

Fake it 'til you make it

this is how u explian a problem

The ending my guy lmfsao

no

why is this sound like API but btw the new ipad pro is our bruh get it for more productive video

said the same thing like 15 times, doesnt explain

The explanation is dead wrong. He is talking about encapsulation. Abstraction is totally different concept.

this is a miss informed video on abstraction which a user has in detail explained, please delete it

Thank You,