Re: Jace. it is stable.

[Marc S Ressl <mressl@macgui.com>]

Hello Brendon (I always keep confusing it with Brandon or Branden... sorry)!

I think JACE and OE go nicely hand in hand. OE attempts to emulate all the
little details of old machines, so you (hopefully) get the same experience
you used to. It does not attempt to be an aid for debugging, so that's where
JACE steps in.

Also, congrats for your work on the RamFactor. I know how hard these things
are, in particular when you are the first who attempts it. It was hard work
to develop a cycle-accurate Videoterm card, but now it pays off as most
other emulations using the MC6845 CRT controller will be extremely easy to
implement. And it is being a lot of hard work to achieve a cycle-accurate
Apple III. I am taking a few days off now, for the same reason you mention:
what's for dinner tonight? ;-D In my particular case the question is a bit
more open: what's life about? :-) I encourage you to make that question, it
gives very satisfying answers!

With the best wishes,

Marc.-

BLuRry wrote:
> On Wednesday, August 29, 2012 9:01:45 AM UTC-5, Marc S Ressl wrote:
>> Hello there,
>> 
>> 
>> 
>> congratulations on achieving that milestone!! I think I understand what
>> this
>> 
>> means, although my project is still quite far away from where I want to
>> be
>> 
>> :-).
> 
> Your project is exciting and awesome and I can't wait to see where
> OpenEmulator goes next!  :-D  Now that I hit this milestone I can try to
> brave the waters to cross-compile it.
> 
>> 
>> In regard to Java, let me point out two things. First, I am writing OE in
>> C++. And second, under special circumstances Java is faster than C++
> 
> Both things are true.  Actually, in raw computation Java is a little
> slower
> in some cases but only slightly.  In reality, the JIT runtime does a
> fantastic job of finding the hotspots of activity and optimizing them on
> the fly to run incredibly fast.  Jace was designed to allocate and keep as
> many objects as possible so that the garbage collector doesn't have to
> chime in much at all.  The memory consumption is fairly stable.  After
> boot
> the only thing you can do that will consume a large chunk of ram is
> throwing a lot of memory to the RamFactor.  The heatmap feature probably
> uses a fair chunk of memory also.  The rest of it is pretty tame.
> 
> The overall goal was to write a well-structured emulator that serves as
> documentation for how this old stuff worked.  By implementing everything
> according to datasheets (for things like the 6522 and 6551 chips), it
> makes
> for a good starting point for someone else to piece together other efforts
> without having to start from scratch.  I like AppleWin for what it is, and
> it is rather nice for an emulator.  However, and it could just be a C++
> thing, looking at the code makes my head hurt.
> 
>> I think the flames have been extinguished now :-).
> 
> Oh, it's a debate without end because everyone is bound to have their own
> opinion.  But there are far more important things to worry about than
> software platform choices of a solitary developer.  Case in point: What is
> for dinner tonight?  That is a much more important concern. ;-)  I don't
> think it is a good topic for this forum as it doesn't apply to 8-bit apple
> computers, unless you're talking about VM2.  (and before anyone asks, no
> jace will never run in VM2 -- that would be silly)
> 
> -B
>