🚀 go-pugleaf

Jamey Graham wrote:
> 

> what a minute!  i have experiencing this problem as maxim.  are you saying
> that the only way to get the performance experienced in JBuilder is to run
> your application in JBuilder?  what about redistribution?  are you're saying
> that for redistribution one should use Javasoft's runtimes??? and jdk1.1.5
> runtimes to boot?  (since jbuilder usings, what, 1.1.2 or 1.1.3)  now i'm
> really coonfused.  would you mind elaborating please?

Relax.  :)  Oh, and don't email me *and* post.  I see duplicates.  It
confuses me, I get grumpy, I don't answer posts, and my co-workers hate me.

Anyways, stock out of the box, the JDK and JREs do not have any
just-in-time compilers built with them.  So, JavaSoft has created what
they call a technology pack one can apply to the JDK and JRE to give you
a JIT.  However, do not apply the pack to JBuilder - we already have
a JIT - use of the other JIT may introduce Java related bugs as it could
be buggy.  We've tested ours with our product, and it's good.

So, when you deploy your app with the JRE, there's no JIT to convert
the interpreted byte code to native code on the fly.  Thus, it's somewhat
slower.  Typically JITs greatest increases are in algorithms and code,
rather than in gui painting and such.

As it is, our JIT is not redistributable.  As for runtimes, you can
use whatever you want.  1.1.5, 1.1.3, 1.1.1, whatever.  They are all
just bug fixes (and some new bugs) on top of the original 1.1.  Don't
get caught in the fear of having to have the latest and greatest.  
Sometimes it's good to wait around with older software that works.



Andrew
--
  Andrew Bennett
  abennett@borland.com

  Due to my workload, personal email more than likely won't get a reply.
  Support options are detailed at http://www.borland.com/devsupport/
  I am unable to answer support questions via email at this time.

  Check http://www.borland.com/devsupport/jbuilder/ for FAQs and
  additional JBuilder support related help.