It appears that we are split down the middle on whether we want a clean slate or build on what we have. Part of the problem is because we are afraid of what it would take to come to consensus. As a result there are some potentially really cool things that we might be able to do with a clean slate that we might not see. There is also the fear that we are abandoning our current users.
First, the reassurances. None of us want to abandon our current users. We aren't all masochistic/sadistic/whateveristic. That is why any brand new development absolutely requires a compatibility layer. Next, the realities. We have an existing framework that works. It has a couple rough edges that we can't clean up because there is current software dependent on it. They are not show-stoppers, but things that stick in some of our craws. Any time we have new contracts that were not there before, we have a new version. It is a question of degrees, but it is a new version nonetheless. Framework Version 4.2 means we keep everything we have already. It means we don't smooth the rough edges. It means we don't do anything radical. Framework Version 5.0 might be a smoking gun. Emotions are high right now, which means that we might have to delay any hopes or dreams for 5.0 even longer. Keep in mind it will always be an emotional prospect. However our attention can't be devided when we are discussing it. We either shoot for the moon, or we play it safe. --------------------------------------------- Introducing NetZero Long Distance 1st month Free! Sign up today at: www.netzerolongdistance.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
