harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodrigo Kumpera <kump...@gmail.com>
Subject Re: Stop this framework/modularity madness!
Date Tue, 17 May 2005 18:28:23 GMT
Maybe this pluggable layer that is not well defined. I think that having 
this as a link time thing is more than enouth. It doesn´t mean that only one 
GC algorithm or JITer will be available at runtime, but all the options 
should be defined when building the JVM.
 Refactoring a system to have a framework emerge is a lot easier, productive 
and produce less cluter. Lets not make generic what doesn't need to be.
 But a better argument is close inspection of this list archive. Seens like 
nobody trully knows how to proper layer a JVM for good modularity. The 
JikesRVM folks are refactoring to make this possible on their JVM, but right 
now they can't really say how it will look when finished.
  Rodrigo
 On 5/17/05, Royce Ausburn <esapersona@gmail.com> wrote: 
> 
> 
> Ack - Sorry about the incomplete mail.
> 
> On 17/05/2005, at 3:58 AM, Rodrigo Kumpera wrote:
> 
> >
> > This must not be the focus until required, so no JIT plugable layer
> > until someone tries to write another JIT for Harmony (emphasis on
> > another).
> >
> 
> In my experience, delaying the 'modular design' of a system causes
> more work. When you rip out the old part, not only do you have to
> design and implement this pluggable layer, this layer probably needs
> alot more design work because you have to consider all the other
> systems that are affected. This also isn't easy because the project
> hasn't been designed in a modular fashion. THen you have to
> reimplement the old part (the JIT bit in your example) - May as well
> design everything to work together in harmony to begin with.
> 
> --Royce
> 
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message