Dalvik seems really interesting to me, even out of the Android platform... It is really an intermediate way between simple VM-based applications and compiled ones.
So I certainly would want it as a standalone technology which would be used as a production platform.
My request now would be to have OSGI running on it.. There is an interesting article about this I enjoy you to read.
A last news : NDK is avaliable to download. NDK means Native Development Toolkit and enables to use C/C++ code with the Dalvik virtual machine.
Showing posts with label java. Show all posts
Showing posts with label java. Show all posts
Monday, June 29, 2009
Sunday, June 21, 2009
Dalvik, running java efficiently
The story of virtual machines is beginning to be quite long ; Smalltalk, Lisp, Java, dotNet, ... The idea behind these were to be able to write once and deploy everywhere. In the case of Smalltalk, it was even a step further by including the concept of "image" which is actually a kind of object oriented database.
The drawback of these approaches is mainly the lack of performance, even if many, many improvements has been made to ensure execution celerity (hotspot for instance)... But the constatation is in front of our eyes : eclipse is still a big processor and memory consummer, microsoft doesn't still write its main applications in dotNet, and so on...
One of the avantage of using VM is that the developper can develop quicker and safer (no more memory leaks for instance). We could easily continue to develop this way but by adding a compilation step we could ensure efficiency. It is what Excelsior proposes, but also IS2T with their Icetea technology.
Google followed the same way by providing the Dalvik technology, ie a VM running .dex files directly got from java .class files. This new format is shorter, quicker, more memory efficient but has not just-in-time compiler. This VM enables Google to run java programs on Android efficiently, and also not to pay fees to Sun ;)
The drawback of these approaches is mainly the lack of performance, even if many, many improvements has been made to ensure execution celerity (hotspot for instance)... But the constatation is in front of our eyes : eclipse is still a big processor and memory consummer, microsoft doesn't still write its main applications in dotNet, and so on...
One of the avantage of using VM is that the developper can develop quicker and safer (no more memory leaks for instance). We could easily continue to develop this way but by adding a compilation step we could ensure efficiency. It is what Excelsior proposes, but also IS2T with their Icetea technology.
Google followed the same way by providing the Dalvik technology, ie a VM running .dex files directly got from java .class files. This new format is shorter, quicker, more memory efficient but has not just-in-time compiler. This VM enables Google to run java programs on Android efficiently, and also not to pay fees to Sun ;)
Monday, December 8, 2008
JSecurity 0.9 out
JSecurity is a java library developped in order to simplify authentication, authorization and cryptography when a client communicates with a server. It seems quite easy to use, even if it lacks a lot of samples. Someone on the restlet mailing list has emitted the idea to adapt Jsecurity with restlets. I'm waiting for discussions on this subject to have a better understanding on the techno. But it seems promising nevertheless.
Subscribe to:
Posts (Atom)