Hi JohnK,

Snippage
>
>Try explaining to a client why he should live with a dog built on a bloated framework (no insult intended to UT framework vendors) :-D

Bloated framework(s) or bloated code should only be a problem in the disk space it occupies and, *possibly*, the swapping it might cause.
Any "intelligence" behind the swapping should easily minimize that aspect.

In other words, bloated code of the framework variety especially, ought *not* to make an app. " a dog " - it can be as bloated as anything but as long as that bloat is not executed *except* when necessary, then bloat should have little impact.

I am still far from settling on/completing a "framework" but when I do I will expect to use that framework, in whole and as-is, in *ALL* my subsequent projects. To me that is the "essence" of OOP. Any other way is, to me, like putting a Rolls Royce front-end on a VW Bug - it ain't a Rolls no matter how you look at it.

Cheers,

Jim N