Amazon has unveiled the details of its development kit for its Kindle e-book reader. The so called “Kindle development kit for active content” (or KDK) will be based on Java 1.4 Personal Basis Profile (JSR 217); custom additional APIs will be available for networking, local storage, specific UI components, etc. (see javadoc). As strongly as
Continue reading Kindle Development Kit to use Java
GWT and JavaScript Date hell
You’d think that in 2010, date processing is something that is easily done in Java (and hence GWT), in a consistent cross-platform way. And you’d be wrong. When I’m talking date processing, I mean simple calendar date (not time) operations, like: get today’s date, add a number of days, compute the number of days between
Continue reading GWT and JavaScript Date hell
James Gossling: “so long, old friend”
This is what James Gossling posted on his blog yesterday… Like so many commenters, I also spent the majority of my professional career with Sun technologies, mostly Java. Whatever happens next, it’s a new era that begins. Fortunately, the company with a big G has embraced Java, and that is probably where the future lies,
Continue reading James Gossling: “so long, old friend”
GWT sighting in Palm’s webOS Mojo SDK
While exploring the code samples that come with Palm’s SDK for webOS (named Mojo), I was pleasantly surprised to see that one of the samples (MojoMsgSample) uses GWT and the Google App Engine for the “cloud” part of the sample! It’s a basic publish/subscribe app, but still it’s nice to find oneself in known territory…
Continue reading GWT sighting in Palm’s webOS Mojo SDK
Google Collections Library 1.0 final
The Google Collections Library 1.0 is a set of new collection types, implementations and related goodness for Java 5 and higher, brought to you by Google. It is a natural extension of the Java Collections Framework. We have finally (Dec 30, 2009) released version 1.0-final! The API is now frozen: there will be no more
Continue reading Google Collections Library 1.0 final
Support the Elvis proposal for Java !
Are you tired of writing (x != null) ? x.getThis() : null Would you rather write something like x?.getThis() If so, support the Elvis proposal for Java ! Interesting alternative notations can be found here.
The future of mobile apps is web apps
This conclusion comes from examining the following facts: modern smartphones are equipped with a recent, state-of-the-art, JavaScript/CSS capable web browser modern smartphones are most often associated with a “always connected” data plan What this means is that if you need to develop a mobile application that should run on several mobile platforms, you have basically
Continue reading The future of mobile apps is web apps
And the winner is.. Palm Pre!
Right the same day I posted an blog entry about my dilemma between Android and Palm Pre for my next phone, I got the latest LUXGSM folder in my mailbox, which features the Palm Pre (“Palm’s very expected tactile phone” according to the folder). So I decided that Android would have to wait, and I
Continue reading And the winner is.. Palm Pre!
This might be my next phone
I’ve been pondering a replacement for my (still reliable but aging) Treo 680. Since I have decided not to get an iPhone as long as the App Store has such insane policies, I’ve narrowed my search down to: Palm Pre An Android device The Pre has a groundbreaking OS called webOS which is almost entirely
Continue reading This might be my next phone
Mark Reinhold’s proposal for Java closures
I believe this proposal, although incomplete, to be much more acceptable to the current Java community than existing BGGA or FCM. Most proposals state that it’s not the syntax that matters, it’s the semantics. While this is undoubtedly true, syntax is the first thing a programmer will see and judge the feature by. If the
Continue reading Mark Reinhold’s proposal for Java closures