It was quite surprising to me to discover this morning the V1.7 of GWT.
Here is the download link.
The release note says :
"(...)adds explicit support for Internet Explorer 8, Firefox 3.5, and Safari 4 as well as a few high-priority bug fixes. In all other respects, it is very similar to GWT 1.6. Note, however, that this release is version 1.7 rather than version 1.6.5 to signify a potentially breaking change for libraries that use deferred binding to specialize code based on user agent (see the next section for technical details)."
Wednesday, July 15, 2009
Wednesday, July 8, 2009
Scala, a nice language
In the universe of development languages, it is very difficult to choose one especially...because it depends on the kind of software you want to develop in one side, and the environmental constraints on the other part. For efficiency, C is still (when well programmed) on the top. For general purpose applications, java or c# are good. For web development on the browser, javascript is almost mandatory, and so on... So the philosophical stone is not yet to be reached.
Nevertheless, I took a glance on Scala few months ago, and I have found it very interesting, concise, agile, and efficient. The learning curve is also quick to learn. Another point is the ability to mix java and scala, and the most important is the disponibility of an eclipse plugin for developping efficiently... So why not using Scala as well?
An interesting article from James Strachan, the creator of Groovy about Scala. At the beginning, I was quite fan of Groovy, but personnaly I think syntax and concepts have evolved in a too complex manner... even if Groovy has powerful features which may match some areas like specific domain languages or metaprogramming.
Nevertheless, I took a glance on Scala few months ago, and I have found it very interesting, concise, agile, and efficient. The learning curve is also quick to learn. Another point is the ability to mix java and scala, and the most important is the disponibility of an eclipse plugin for developping efficiently... So why not using Scala as well?
An interesting article from James Strachan, the creator of Groovy about Scala. At the beginning, I was quite fan of Groovy, but personnaly I think syntax and concepts have evolved in a too complex manner... even if Groovy has powerful features which may match some areas like specific domain languages or metaprogramming.
Monday, June 29, 2009
Dalvik request
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.
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.
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 ;)
Wednesday, April 8, 2009
Google big knock
Google has gone a step forward yesterday by providing us yesterday with three main technology pepites, ie the delivery of GWT 1.6, the GWT eclipse pluggin working with it, and the App engine for java (up to now we have had App engine for Python).
With these three corner stones, Google is able to offer to developpers a complete framework for developping free or commercial solutions without having to think about the server performance, the data recovery, the deployement headaches, and so on... or just to make quickly mockups.
You can find further informations here :
With these three corner stones, Google is able to offer to developpers a complete framework for developping free or commercial solutions without having to think about the server performance, the data recovery, the deployement headaches, and so on... or just to make quickly mockups.
You can find further informations here :
Monday, April 6, 2009
GWT 1.6 RC2 available
The second release candidate of GWT1.6 is out and can be downloaded here :
"The GWT team is happy to announce the availability of Google Web Toolkit 1.6
RC2. Download it here:
We have just from now to wait for the conformance of external tools and libraries to work on it :-( .
"The GWT team is happy to announce the availability of Google Web Toolkit 1.6
RC2. Download it here:
http://code.google.com/p/google-web-toolkit/downloads/list?q=1.6.3
For an overview of the new features in 1.6, please see the announcement:
http://googlewebtoolkit.blogspot.com/2009/03/google-web-toolkit-16-rc...
The only real difference from RC1 should be some fixes I made for the hosted
mode Jetty configuration issues that were reported with RC1:
http://code.google.com/p/google-web-toolkit/issues/list?can=2&q=miles...
We have just from now to wait for the conformance of external tools and libraries to work on it :-( .
Saturday, March 7, 2009
Flex is declared as "strong prositive" by Gartner
I'm personaly fond of GWT, but I read on an IT magazine yesterday that according to Gartners, GWT (and also JFX) were only declared "promising"... Silverlight, Laszlo, and several JS libraries were "positive" technologies....
It is obviously only a comment from one the most known consulting cabinet...but it makes us thinking of the fundaments of our "faith" in such or such technology... In fine we never must be a "ialatollah" of a technology, but still continuing to look around us and choose a language, a framework, a libray, a pattern, ..., only according to the context in which we have to make a decision.
The equation is each time different, and unknown values/constants too.
Actually, why not Flex or AIR instead of GWT....according to the context?
It is obviously only a comment from one the most known consulting cabinet...but it makes us thinking of the fundaments of our "faith" in such or such technology... In fine we never must be a "ialatollah" of a technology, but still continuing to look around us and choose a language, a framework, a libray, a pattern, ..., only according to the context in which we have to make a decision.
The equation is each time different, and unknown values/constants too.
Actually, why not Flex or AIR instead of GWT....according to the context?
Subscribe to:
Posts (Atom)
Posts
