Others have done well here, but I'll give it a go too, in procedural terms. Objects are just a style of programming. As our program begins to process different

Others have done well here, but I'll give it a go too, in procedural terms. Objects are just a style of programming. As our program begins to process different types of data, we begin to see that some data always goes together and tends to hit certain branches of code together. This is because the code and the data together form an implicit model of how a particular kind of data should be handled. Object orientation makes this explicit. We can store a little namespace of data in an object, and also give it a way to find the right code to run when it receives a 'message'. Then we can start to think of our program as a cascade of 'messages' between objects.