vendredi 15 octobre 2010

Veille technologique semaine 41


Pour le bulletin de la semaine 41, je vous propose les sujets suivants :
  • Oracle et IBM viennent de s'associer pour le développement de Java sur l'implémentation OpenJDK. C'est une annonce très importante car elle exprime le soutient de deux poids lourds pour la plateforme Java. Plusieurs articles avec des commentaires.
  • La dette technique : une explication et des propositions de solutions
  • Le model driven : mais où sont les succès ?
  • Les 15 leçons apprises sur la pratique du model driven.
  • Conférence JavaOne 2010 : le JDK 7 et le JDK 8
  • JavaOne 2010 : le garbage collector et les myths
  • JavaOne 2010 : Aparapi (A PARallel API) : une API pour la programmation parallèle des processeur graphique (Graphic Processor Unit : GPU) proposé par AMD.
Bonne lecture.

IBM Joins the OpenJDK Project!
Posted by editor on October 11, 2010 at 1:24 PM PDT
Oracle and IBM have announced that IBM is joining the OpenJDK project:
the companies will collaborate to allow developers and customers to build and innovate based on existing Java investments and the OpenJDK reference implementation. Specifically, the companies will collaborate in the OpenJDK community to develop the leading open source Java environment.
With today's news, the two companies will make the OpenJDK community the primary location for open source Java SE development. The Java Community Process (JCP) will continue to be the primary standards body for Java specification work and both companies will work to continue to enhance the JCP.
The collaboration will center on the OpenJDK project, the open source implementation of the Java Platform, Standard Edition (Java SE) specification, the Java Language, the Java Development Kit (JDK) and the Java Runtime Environment (JRE).
Rod Smith, Vice President, Emerging Technologies, IBM, said:
IBM, Oracle and other members of the Java community working collaboratively in OpenJDK will accelerate the innovation in the Java platform. Oracle and IBM's collaboration also signals to enterprise customers that they can continue to rely on the Java community to deliver more open, flexible and innovative new technologies to help grow their business.
For additional commentary on this news, see:

IBM joins OpenJDK: A big day for Java
Filed under: javase jdk jdk7 jdk8

Big news today. Wow.

IBM is joining the OpenJDK !

There's already a welcome note, and here's the joint press release, and more here from The Aquarium. But what does it really mean ?
  • It means that IBM will be joining Oracle engineers working on the roadmap for JDK 7 and 8 for OpenJDK.
  • It means that IBM's long involvement in the Java platform can be orders of magnitude deeper than it has even been before.
  • It means that IBMs engineers will be contributing their valuable fixes, code, optimsations directly into the OpenJDK platform
  • It means that OpenJDK will be the primary venue for Java SE impementation code: Direct, open discussions in the mailing lists + quicker fixes + better quality = better code.

And it will still leave plenty of room for Oracle's JDK (which is of course based on OpenJDK code) and IBM's SDK to compete on other aspects of the platform than the core libraries: tuning, tools, deployment and so on.

A new era of co-oper-tition !

There's going to be a bunch more information following today's initial news, stay tuned.

And stay tuned for the long awaited JSR for Java SE. Really coming soon.


There's not a moment to lose!
Mark Reinhold's Blog
IBM to join OpenJDK

I'm very pleased that IBM and Oracle are going to work more closely together, and that we're going to do so in the OpenJDK Community. IBM engineers will soon be working directly alongside Oracle engineers, as well as many other contributors, on the Java SE Platform reference implementation—starting withJDK 7.
I expect IBM's engineers to contribute primarily to the class libraries, working with the rest of us toward a common source base for use atop multiple Java virtual machines. We each have significant ongoing investments in our respective JVMs; that's where most of the enterprise-level feature differentiation between our respective products is found, and it makes sense for that to continue. Focusing our efforts on a single source base for the class libraries will accelerate the overall rate of innovation in the JDK, improve quality and performance, and enhance compatibility across all implementations.
Our tighter collaboration will be evident not just in OpenJDK but also in the Java Community Process. IBM has endorsed Oracle's proposal for Java SE 7 and Java SE 8, which already has strong support from across the community. We'll also join forces to enhance the Java Community Process so that it remains the primary standards body for Java specifications.
This is excellent news, for the Java SE Platform and for OpenJDK. I've gotten to know many of IBM's top Java engineers over the years, and I now look forward to working more closely with them.

IBM and Oracle to Collaborate on OpenJDK
  Posted by pelegri in General

Today, IBM and Oracle announced their intent to work together to accelerate innovation on the Java Platform, leveraging OpenJDK.
This is great news; IBM has been a pillar in the Java ecosystem since Dec, 1995 when they became a licensee(web.archive.org) and their commitment includes participation and leadership in JSRs, participation in the JCP EC, investment in community activities and projects, and a multitude of products and tools built on the Java platform. The new arrangement should indeed provide an acceleration of the development of the platform.
Today's announcements have these main components:

• IBM and Oracle will work together to make OpenJDK the primary forum for Open Source Java SE Development
• IBM and Oracle are committed to accelerate the pace of evolution of the Java Platform, and will jointly support the Java SE 7 and Java SE 8 schedule proposed at JavaOne and elaborated yesterday by Mark andHenrik.
• IBM and Oracle will work together to continue to enhance the JCP, which remains the primary standards body for work on Java Specifications.

Exciting times ahead. I expect plenty of reactions to this announcement through the next couple of days and I will update this entry to record them.
Main Links:

Reactions

Technical Debt a Perspective for Managers
It's iteration 10 and your project is starting to slow down. For the past few iterations the team hasn't been able to complete quite as many stories as they did in the past. In addition, more bugs have been recently found both in the new stories and also in regressions. The manager knows that the team members haven't changed and they're still working the same hours. The customer is asking "What happened? Is the team still working hard?"


Model-Driven Development: Where are the Successes?
experiences from using model-based development in industry from the EA-MDE project. The project is interested in understanding the factors that lead to success or failure with model-driven engineering (MDE) to help design the next generation of MDE tools. This question is not new, two years ago, Sven Efftinge, Peter Friese and Jan Köhnlein published an article "MDD best practices and Johan Den Haan, CTO of Mendix, published an article on the how an MDD initiative could fail. Adopting an MDE approach can be quite daunting.

Then, Johan concluded his article by:
It's not my goal to discourage you from starting with model-driven software development. I just wanted to show you the complexity of it and wanted to share some thoughts hopefully pointing you at directions helping you to overcome the complexity of MDE.


15 lessons learned during the development of a Model Driven Software Factory
Do you believe in Model Driven Software Development? Do you believe in modeling languages on a higher abstraction level and automated transformations to an executable business application?

I see Model Driven Software Development as an important part of the future of software development. However, I also see a lot of people struggle with actually using Model-Driven techniques and applying them in their daily business. It isn't trivial to build a successful Model-Driven Software factory (MDSF). In this article I want to share 15 lessons I learned during the development of a successful Model Driven Software Factory.
For more background information about Model Driven Software Factories or designing Domain Specific Languages please read the linked articles first. In short: a Model Driven Software Factory let's you design a software application using high
level models. These models are automatically translated into a working software application.

So, what's important to remember when building your own Model Driven Software Factory?


JavaOne 2010: Upcoming Java Features
In the Java booth, Jim Holmlund gave me an overview of upcoming features in Java. (Luckily for me, he had a copy of the speaker's slides. So it made up for the session I missed in the morning.)
Some of what's coming is pretty cool. Some is a bit dissapointing, compared to what I was hoping for. Here's my notes:

Java 7
  • Strings in Switch Statements
  • Underscores in constants
  • Multi-catch
  • Autoclose interface
  • Default methods for interfaces
  • Type "Inferencing"

Java 8(ish)
  • VM Support for Dynamic Languages:
  • LambdaJ:


JavaOne 2010: The Garbage Collection Mythbusters
As members of the Garbage Collector Group of the HotSpot Virtual Machine Development Team, John Coomes and Tony Printezis have the credentials for presenting "The Garbage Collection Mythbusters" at JavaOne 2010. The speakers took turns talking and they started by Coomes stating they wanted to "cover the strengths and weaknesses of Java garbage collection or at least the perceived strengths and weaknesses of Java garbage collection." They then proceeded to provide a brief background ("refresher course") into the basics of garbage collection.



Aparapi: New, "Pure Java" API for Executing Arbitrary Compute Tasks on GPUs Unveiled at JavaOne
This week Gary Frost from AMD unveiled an alpha release of Aparapi (A PARallel API), an API that allows programmers to write logic in Java to be executed on a GPU. GPUs are the massively parallel hardware acceleration chips originally installed in PCs to boost graphics rendering performance but that are now pushed to other kinds of compute-intensive tasks that have nothing to do with graphics.

Publié par à

Aucun commentaire:

Enregistrer un commentaire

Inscription à : Publier les commentaires (Atom)