My thoughts on this article can be summed up very breifly. It is a very interesting concept, and not one that hasn't ever crossed my mind. And I think that it would be a useful tools to understand the code better. With newly implemented Object Oriented Programming, the "view based" model of coding doesn't really apply anymore, it's not the ONLY way to think about things...

But, this idea of making the practice of OOP actually object oriented may cause some problems. I think that the initial programs that allow for OOP coding to be Object Oriented would limit the possibilities of coding. And, although it shouldn't, the format might not be able to accomplish the same goals in the same efficient way. I think that these first products would be so terrible to use that the concept would never catch on...

Remember that a new tool is most often cumbersome at first. With time, it can be the most effective system around. I am sure OOP was thought of as slow and "on-crack" at first but it is now an industry standard. Don't limit trying because of possible failure (at least that is my motto).