Hi,
I agree with Otan , it is only a question of time to be appreciated what
it's worth.

H2 is a young and beautiful piece of work that surprises me everyday
with what they can do compared to traditional databases.
I believe H2 has much potential to exploit and statistics can show this.

My only concern is that this derivation dilute or delay the growth and
maturation of H2.

Regards,
Dario.


El 23/03/10 02:20, Otan escribió:
> Hi Thomas,
>
> Question: Would you continue maintaining the Java version of H2 side
> by side with the C version?
>
> BTW, I believe H2 is not a substandard or an inferior product. Give it
> proper marketing and publicity, maybe its community will grow and
> surpass Apache Derby/JavaDB.
>
> /Otan
>
>
> On 23 March 2010 02:47, Thomas Mueller <[email protected]
> <mailto:[email protected]>> wrote:
>
>     Hi,
>
>     > I was curious to know why you are planning to do this?
>     > Might I say, I'm a little disappointed? :)
>
>     There are multiple reasons. First, I always wanted to be able to use
>     H2 without JVM. Not necessarily a fast, but a working version. Earlier
>     versions of H2 included a native version (compiled using GCJ).
>     However, there were problems, maybe due to GCJ (not sure) or how I
>     used it. So I removed the GCJ version.
>
>     The advantages of a native version of H2 are:
>
>     * fast startup
>     * smaller size
>     * easier to integrate in other languages / platforms / applications
>
>     If you look at SQLite, you will see there is a need for that:
>
>     https://www.ohloh.net/p/h2database (44 users)
>     https://www.ohloh.net/p/sqlite (912 users)
>
>     Now, in another project I'm working on (Apache Jackrabbit) there is
>     also a need for a native version. Not necessarily the whole project,
>     but probably a subset. For similar reasons than those of H2.
>
>     The best language for that is probably C. My idea is to have a
>     converter from Java to C so that a large part of the code can be
>     converted to C. The resulting code doesn't necessarily need to be fast
>     - the performance critical part could be written in C (written twice).
>     Not sure if it will be written twice, but it could.
>
>     I already wrote a Java to C converter about 10 years ago. This was to
>     run another Java database (PointBase Micro) on cell phones. The code
>     was ugly, so I threw it away. But it was working. It was never used in
>     production for political reasons.
>
>     Now my plan is to again write such a converter.
>
>     Regards,
>     Thomas
>
>     --
>     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.

-- 
Saludos,
Dario 

-- 
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