http://userscripts.org/scripts/show/43404

Deleting all my FaceBook friends

Three Advantages of Object Oriented Programming over Procedural Programming
Object Oriented Programming (OOP) was created because programmers wanted a way in which to more accurately model the real world. This was achieved through the creation of “Objects”. Objects encapsulate data and the methods needed to process the data held within. It was soon found that there were many advantages of OOP over procedural programming:
1. Ease of Modification: With procedural programming, if one was to change a procedure or a data set within the code, it could create real problems further down the line. Multiple sets of code could access and modify one set of data, if one set of code relied on a certain data set to be unchanged, problems could be encountered where the code would not be able to use the data that had been altered. In OOP data and code are kept within the bounds of objects. The information held within the object is kept hidden (encapsulated) from the rest of the system. This results in ease of modification as data can be changed within one object without affecting the rest of the system.
Example:
If you were to model a typical street, the street would be full of houses, each house is an object. They would all be instances of a “House” class, whilst each would have its own separate attributes. As houses can either decay or just become unfavoured by its owners, it can be demolished and be replaced by another house, with the same inherited attributes as the “House” class but with entirely different attributes as the house that it replaced. The same can happen within a software system or application. Objects can be removed and replaced with little or no effect on the rest of the system.
2. Better at Modeling the Real World: OOP languages are much better at modeling the real world because of the use of classes and objects as representations of real world “objects”. OOP Objects can be made to interact with other objects just as in the real world. I.e. A customer object can use a payment object when dealing with a salesperson object. All the information regarding each object is encapsulated within each object, just as in the real world. Each object can message another to request processed data, such as an organisation object querying a supplier object regarding available stock items. Procedural programming really cannot achieve this with such simplicity because of the lack of real world modeling.