In principle I agree with Slin
The "components" based programming model has become more and more popular in the comunity of professional developers so it must have some advantages over the traditional hierarchy based model, I suppose in term of code reusability and efficiency
However I find it a non intuitive and non elegant programming style
First of all you must instance abstracted rather than concrete objects
Take for example the object trasform as an instances of the class Transform
Moreover I dont like the use of auxiliary function for data exchange among components attached to the same entity or even worse attached to other objects
How ugly it is :

transform.Find("Hand").GetComponent(OtherScript).DoSomething("Hello");

Unity supply a relatively user friendly version but if you consider a pure component based engine such as Torque 3d I am sure that many components supporters will change their mind