>>>However there may be the individuals who changed the jobs where different frameworks were the standard, and such people might know several frameworks thorougly.
>>
>>Hi Nick,
>>In cases like that, you begin to learn the new framework and your skills with the previous framework begin to deteriorate. You would no longer follow the progression of the other framework so would be out of date very quickly.
>>
>>My point was that many have tried several frameworks but I don't know of any who are fluent in more than 1 or 2 at a time. If you are an independent, you know one or two and use those. Corporate life is usually entrenched in one framework. If you bounce around, you may have been an expert in a particular framework at the time, but 18 months later and a version upgrade or two, and I don't see the expert status remaining.
>>
>>This is all my opinion and if there are framework "supermen/superwomen" out there who use three or more frameworks on a regular basis, I SALUTE YOU!!
>>
>>>I myself worked with 2 frameworks - Codebook 3.0,(which I didn't like :) and Visual Extend 5 and 6 (Which I mostly like, however sometimes it might be slow because it's very elaborated and has a lot of code in base classes).
>>>
>>
>>Why didn't you like Codebook? Do you think you would like any of the Codebook offspring? I think MM and VFE have their roots sprouting from this tree (I could be wrong).
>
>I found it too heavy and dog slow. I know that it's approach was right, but the result (speed) was wrong. :) You also could (for example) easily forget in a month how have you created that object-oriented menu. I think that's why MM is called "Codebook for Mere Mortals." :) If I have some spare time I would like to take a look at CodeMine framework, which as I've heard is one of the lightest ones.

Nick,

Having a lightweight framework is important. But having a framework that is scaleable is just as important. Whereas Flash Codebook is probably the heaviest of them all (What the hell is i-layer really for anyway?), MM is kind supercharged version of Flash Codebook. I have to admit, MM business objects are a bit heavier than they need to be. Why bother with the cBehavior object? Do bizobjs really need to be based upon containers? Do the dataenvironment classes realy need to be that heavy? I havn't seen the next version, and I hope some of these issues will be addressed. What I can say about MM is that it really is scaleable. It also provides an awlful lot of flexibility. My only critisism is that I believe it could be even lighter if some of the old Codebook paradigms are dropped. Codebook was a great idea and far ahead of its time. But now the time has come for Codebook to adjust for the present. I believe MM will do just that, but no framework is perfect...