>>.... I'm not trying to tell everyone to go back to punch-cards, COBOL and VFP .. all of those ancient, pre-industrial languages.. <g> <

Hey, watch it you young whipper-snapper. I know a veiled dig at me when I see it!! <g>




>>Wow, this is one of longest thread I've read. My feeling is that this entire convensation has nothing to do with Mere Mortals. Keep referring to Kevin is not fair to him. I think this thread should have been titled "Real Programmer Don't Use Framework" and move to the chatter section.
>>
>>And "Real Programmers" shouldn't use 3rd party controls or libraries either, every single line of code must be written by them personally.
>
>See, now is that a <g> or what? I mean... don't be ridiculous. I don't think people should re-invent the wheel. If people will just read. I think a framework is ideal for small projects, where time constraints are factory. If you have luxury of time, the benefits of writing your own framework are worth it.
>
>I think the knowledge the team gains from developing their own framework is priceless, and more then worthwhile to dedicate a month or two to doing it. Not only does give them the knowledge, the performance, customizability, and the simpler your own framework will probably be.
>
>I think it outweighs it. If you already have the knowledge of a framework, and you are comfortable that a commerical framework would totally fit into your large scale application then it may be worth it. You are then somewhat married to it. Like Jason said, it is like hiring another employee. If the employee turns out to work well and everything is smooth, it was worth it. If you have problems with the employee, but rely heavy on them for your application and business, it is more difficult to get rid of them.
>
>That was the point, I'm not trying to tell everyone to go back to punch-cards, COBOL and VFP .. all of those ancient, pre-industrial languages.. <g>
>
>Morgan