Class S

If you are going to Say it was the OS exclusivity, wrong. During the 90's Apple licensed their OS out to other companies and their reputation for quality went down the drain, which is why they don't license their OS out anymore. source

I don't know, I thought after the 70's those stalk shifters would be a thing of the past. I would love to see the new S-Class without a proper center shifter, however doubtful, especially since its made its way down to the new E. source

Yes, Managers and Reps have been leaving and I don't blame them! It's going to be hard to find something else, you have NO sales numbers to show on your resume or discuss during your interviews, we are sales people, that's what they are going to be looking for I'm sure. source

In all reality, do you really care if you get that event fired back at you? It allows you to handle any times the Model is changed outside the Panel and there really isn't a lot of overhead involved in checking to see if you actually have to update the value. The PropertyChangeEvent holds the property being changed as well as the old and new values. You can check each incoming event to see if the value in the Panel is the same as the new value, and if it is then discard that event. The Model should tell everyone that is listening to it for PropertyChangeEvents every time it has changed otherwise it will need to know too much about the Objects that are listening to it. Whatever you do, DO NOT create property change event listener loops. You will end up with a situation that very easily can end in an infinite loop if you are not very careful. source

PHP does not allow multiple inheritance, but you can do with implementing multiple interfaces. If the implementation is "heavy", provide skeletal implementation for each interface in a seperate class. Then, you can delegate all interface class to these skeletal implementations via object containment . source