I am a bit surprised that this was not all pretty well worked out in detail before the merger. Why not first take the time to see what will need to be done and what the result will look like before deciding to do it? That should not be a daunting task. A list of what the result will take and what the result will look like would be worth having before taking a vote on this. To just a make a decision and to start coding blindly before knowing what the parameters of the situation are would be just to return to past "throw it against the wall and see what sticks" sort of decision making.
The continuing introduction of "Ti" into these conversations is confusing to me. I am not sure what Ted means by that. I know Ted and I know it is an agenda for sure, but I don't know what that agenda is. I also don't see the arguments (reasons) for evolution now revolution later decisions. Are there any that have been gathered, arranged, collated, etc? This all seems a bit out of control and not well-planned. These sorts of discussion, by the way, have nothing to do with "architecture". On 5/7/06, Ted Husted <[EMAIL PROTECTED]> wrote:
On 5/6/06, Bob Lee <[EMAIL PROTECTED]> wrote: > The new API should be simpler, cleaner, better separated from the > implementation, more intuitive, and better organized. If you > understand WW2, you'll have no problem understanding the new API. If > you haven't learned WW2 yet, it will be easier to learn the new API > than WW2. All of which seems to imply that the "new API" might be the equivalent of WW 3. We've always planned to consider signficant API changes for "SAF 2.0 Next" as Ti Phase 2, but we need to set modest, achievable expectations for SAF 2.0 (aka WW 2.3). The first phase is an evolutionary transition. The second phase is meant to be revolutionary. Of course, without code on the table, it's too soon to say yes, no, or maybe. No matter what anyone plans to do, the implementation has to pass muster. The most anyone here can say is "Looks cool, show us the code" or "Here's the code, how do you like it?". -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~
