Hi Tom..

Interesting view points (no pun intended...)

With respect to complexity, I see your point there. I see that cutting both ways. On one hand, getting data is easy and less complex with RV's. However, the problems with update conflicts, scalability, etc, are more complex to solve with RV's.

The previous issue goes directly to cost. The more you have to make the square peg fit in the round hole, the more the solution will cost you.

What I am interested in is what specific user requirements forced you to go to views. Of course, if a user wanted you to use/adopt a particular framework, then I see why you elected to use views; you simply don't have much of a choice there.

I find it interesting that when it is all said and done, you prefer SPT over views. From a technical standpoint, I think this is a good choice. That is why I think you will like Dataclas. It will address a lot of your concerns, and at the same time, let you use SPT.

I have concluded that solid technical arguments for RV's do not exist. There are arguments, but they easily dismantled.

Best of luck!