No worries mate.
But if JRockit is optimized for performance does that mean that it does all the same things that the other jvms do but just performs better?
If so then how come everybody isn't using it?
Usually when something is optimized for performance it is taken away from something else. And databases have taught me that it is usually taken away from consistency, correctness and elegance :-)

- Rami

Marc Chanliau wrote:
Rami, I'm not disagreeing with you. Any JVM implementation should be per JVM spec, of course otherwise it would defeat the very purpose of Java, as you rightfully note. What I'm saying is that some JVM implementations may be more optimized for some tasks, for example, JRockit is optimized for performance.

On Wed, Nov 10, 2010 at 10:08 AM, Rami <[email protected] <mailto:[email protected]>> wrote:

    > I disagree that having one JVM " that works the same on all
    OS's" as is said below, is a good thing. Choice is better
    (HotSpot, JRockit, etc.).

    Very well, but bear in mind that the creators of java had that
    particular idea as the main reason to introduce java
    http://en.wikipedia.org/wiki/Write_once,_run_anywhere

    And that proposition would have the most benefits if it could be
    delivered on the client side.
    Because over your server environment you have complete control.

    Frankly, I would have no problem sticking with jdk 1.6 for years
    to come,
    if I could trust that those programs run the same on all 3
    operating systems.

    - Rami

    Marc Chanliau wrote:
    Java will always be available on the Mac, only it won't be
    provided by Apple (as of Lion), which is really a good thing (so
    no need to move from Mac to Linux). On the Mac, there are
    alternative solutions out there as of today (SoyLatte, OpenJDK),
    and these solutions will become even better over time. I disagree
    that having one JVM " that works the same on all OS's" as is said
    below, is a good thing. Choice is better (HotSpot, JRockit,
    etc.). BTW, most Java apps are on the server, not on the client
    (Swing / SWT vs web apps), so you can use OpenJDK on the Mac
    today without any risk. Last but not least, in the future (Lion)
    the Mac will be up-to-date as far as the JVM instead of being two
    years behind as was the case with JDK6 (OpenJDK7 will be
    available soon, it's already available today for early adopters).
    Apple is pulling out of everything that is not "Apple". The
    next casualty will be Ruby (for example, the TK libraries to
    build client Mac (Cocoa) apps are not bundled with the Mac (Snow
    Leopard) anymore, you have to install TK yourself now (no big
    deal, but disturbing trend). Apple's point is that if you want to
    develop Cocoa apps you should use Objective-C (which will
    probably be the only language accepted in the forthcoming Mac App
    Store).
    Just my two cents...

    On Wed, Nov 10, 2010 at 8:56 AM, Dario Fassi <[email protected]
    <mailto:[email protected]>> wrote:

        I agree. What they are doing is spitting up.
        Lately, every time the big players try to use their position
        of power to drive the market, the only thing they do is
        strengthen the migration to open source technologies: Linux
        servers & desktops, java, php, postgresql, etc.

        El 10/11/10 10:23, Rami Ojares escribió:
        > It was actually good news for compatibility on windows when
        MSJVM was ditched in favor of Sun's jvm.
        > It's better to build one jvm that works the same on all OS's.
        >
        > On 10.11.2010 14:45, Wildam Martin wrote:
        >> However, my personal opinion is: Apple hasn't yet the
        market share
        >> that Microsoft does, but (already) behaves similar, so it
        is to avoid.
        >> I know other developers sucessfully switched from Mac to
        Linux. I
        >> personally came from Windows world but did the same.
        >>
        >

        --
        You received this message because you are subscribed to the
        Google Groups "H2 Database" group.
        To post to this group, send email to
        [email protected]
        <mailto:[email protected]>.
        To unsubscribe from this group, send email to
        [email protected]
        <mailto:h2-database%[email protected]>.
        For more options, visit this group at
        http://groups.google.com/group/h2-database?hl=en.


-- You received this message because you are subscribed to the
    Google Groups "H2 Database" group.
    To post to this group, send email to [email protected]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/h2-database?hl=en.
-- You received this message because you are subscribed to the Google
    Groups "H2 Database" group.
    To post to this group, send email to [email protected]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:h2-database%[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/h2-database?hl=en.


--
You received this message because you are subscribed to the Google Groups "H2 Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.

--
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en.

Reply via email to