OO works great for large projects.
I have converted small elegant programs from functional to OO with dismal results.
As a OO programmer, I have found that the most important design and code techniques come from Structural programming. Most of the powerful design patterns can be related to things done Functionally, but by using OO techniques. Heck I think the Observer pattern is nothing more than a smart GOTO.
I have seen some OO designs with classes containing nothing but attributes (Data Objects) and classes containing nothing but methods (Editor Objects).
Why not. The problem with OO projects is that designs get rejected for not being OO enough.
In summary - good OO does not reject or ignore structural programming - it attempts to stand on the shoulders of structural programming to achieve maintainable industrial strength programs.