You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Craig R. McClanahan" <cm...@mytownnet.com> on 2000/01/12 01:52:14 UTC

Re: You have to break eggs to make an omlette [was: LONG TERMPLAN]

rubys@us.ibm.com wrote:

>
> So what I am likely to do?  That's easy - I'm likely to sit out for the
> duration.  I can't speak for others, but there is a distinct possibility
> that some others may feel this way too.
>

Unfortunately, that's an argument that cuts both ways.  I'm certainly not
excited about expending the effort it would take to incrementally modify the
fundamental architecture with the baseline requirement that it always has to
work.

To say nothing of the fact that you are likely to focus on the day-to-day
integration challenges and not pay sufficient attention to where you are trying
to get.

>
> - Sam Ruby
>

Craig

PS:  Can we stop breaking eggs and making omelettes pretty soon?  Gotta watch
my cholesterol level :-).



Re: You have to break eggs to make an omlette [was: LONG TERMPLAN]

Posted by James Todd <jw...@pacbell.net>.


"Craig R. McClanahan" wrote:

> To say nothing of the fact that you are likely to focus on the day-to-day
> integration challenges and not pay sufficient attention to where you are trying
> to get.

well stated. a good part of the tomcat 2.2 stuff i had my mits on is
a result of meeting some pretty aggresive goals ... typical proto type
cycle.. with the initial goals (servlet 2.2 compliance for the most part,
j2ee integration and jakarta) knocked down i was *very* eager to
get in and re-design. hell, i was basically drooling ... with all sorts of
ideas i formulated over time and was eager to toy with ... till a career
change came upon the scene that is. "you get it right the third time"
(brookes) does seem to be accurate in my experience.

sometimes one needs to step to the side a bit (eg *.next) to see
the proper design/proto/play/bring back to the table in order to
amp up the momentum a notch ... for the better. perhaps communicating
about components/subsystems vs tomcat foo.bar and putting the
burden on the *next (or whatever it is called) path to track the
fixes are all that is required.

- james