Hi, > so nothing gained with the faster startup of H2
Except if the application is not written in Java. Or also converted to C. > Java 7 will even address startup due to increased modularity. Well, let's see what happens to Java and the specially the JVM. Most likely the acquisition by Oracle will be good *and* bad. > I could have returned to C but I have chosen Java for good reasons I'm not saying Java is bad. It has many advantages over C. > Before building your own Java -> C translator, will you be investigating > existing options, or do you just want to write your own because it would be > fun? In a way it's fun :-) I didn't know about vishia.org, I will have a look. It seems to be more geared towards C++ lately, but let's see. I do speak German so working with them is not a problem for me. JCGO: it's commercial, therefore not an option. > only require a subset of the code to be working. Most likely the converter will (at least first) not be used for H2, but for other things. H2 is not the main 'driver' behind the Java to C converter, it's the Jackrabbit project. For me, a C version of H2 is not urgent. I started to write the Java to C converter within the H2 project because I can't work on it on company time (once it's used I can charge for it :-). The future of the Java to C converter is relatively open. > Sun releasing a Java to objective C converter for the iPhone I read about converters, but they are all commercial. Do you know about a (another) free / open source project? > Would you continue maintaining the Java version of H2 side by side with the C > version? No. The plan is to only maintain the Java version. The main branch will stay Java, yes. The Java to C converter should produce code that doesn't need to be maintained manually. The Java to C converter should be part of the build process. There will probably be some C code in addition, but it shouldn't be much, and it shouldn't be code duplication. The plan is _not_: convert H2 to C, throw away the Java code, and then continue working on the C code. The plan is, and always was, work on the Java version. > maybe its community will grow and surpass Apache Derby/JavaDB. I believe the community already is at about the same level than Apache Derby and HSQLDB. And it is growing, while I'm not sure about the community of the other Java databases. This is just my personal view. I believe Apache Derby, and specially HSQLDB, still have a higher market share however. > The Lift web framework (written in Scala) now comes configured by default to > use h2. That's good to know! I like Scala, and maybe I will convert H2 to Scala sometime in the future (hopefully somebody will write a Scala to Java converter :-) > the C version won't (probably) be stable If the conversion is correct, then it should be stable. Building a correct converter is of course a challenge :-) As I wrote, it's a long term project. 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]. 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.
