Pour le bulletin de la semaine 39, je vous propose les sujets suivants :
La journée du « Model Driven » : 25 novembre 2010, Paris
Les principaux acteurs du MDA
Blu Age, Jaxio, Mia-Software, Obeo, Objecteering Software, Objet Direct, Microsoft, Sodius, SoftFluent, W4 vous invitent à la 4ème édition du MD Day, la journée consacrée aux approches « Model Driven .
Une rencontre unique pour échanger, confronter les retours d'expérience et enrichir sa vision des approches du Model-Driven.
Nouveauté cette année : l'agilité sera au cœur des conférences
Principaux temps forts : intervention de Steve Cook, Membre de l'OMG ; table ronde avec des acteurs incontournables de l'agilité comme Laurent Bossavit, Spécialiste des approches Agiles et d'Extreme Programming, Christophe Thibaut, Coach Agile chez OCTO Technology, entre autres.
Outre l'agilité, bon nombre d'autres thèmes seront abordés : modélisation fonctionnelle, génération de code, modernisation du SI, orchestration de processus métier, exécution des modèles, DDD Domain Driven Design, choix entre UML et DSL, ..
Site web :
www.mdday.fr
Le programme :
http://www.mdday.fr/programme.htm
inscription obligatoire sur le site :
register.mdday.fr/seminaire/viewRegisterForm.do
OpenOffice.org divorce et devient LibreOffice
Le couple OpenOffice.org / Oracle a divorcé. La communauté en charge du développement de la suite bureautique open source souhaite voler de ses propres ailes, sans la tutelle d'une entreprise commerciale.
Le développement d'OpenOffice.org (Ooo) était depuis 10 ans réalisé par des volontaires et des entreprises, mais sous l'égide de Sun. Le rachat de ce dernier par Oracle n'a visiblement pas rassuré la communauté Ooo. L'entreprise de Larry
Ellison aurait considéré ce groupe comme faisant davantage "partie du problème que de la solution" a commenté Charles-H. Schulz, l'un des membres d'OOo.
There is no Plan B: why the IPv4-to-IPv6 transition will be ugly
Twenty years ago, the fastest Internet backbone links were 1.5Mbps. Today we argue whether that's a fast enough minimum to connect home users. In 1993, 1.3 million machines were connected to the Internet. By this past summer, that number had risen to 769 million. and this only counts systems that have DNS names. The notion of a computer that is not connected to the Internet is patently absurd these days.
But all of this rapid progress is going to slow in the next few years. The internet will soon be sailing in very rough seas, as it's about to run out of addresses, needing to be gutted and reconfigured for continued growth in the second half of the 2010s and beyond. Originally, the idea was that this upgrade would happen quietly in the background, but over the past few years, it has become clear that the change from the current Internet Protocol version 4, which is quickly running out of addresses, to the new version 6 will be quite a messy affair.
JavaOne 2010
La version 2010 de JavaOne, sans doute la plus grosse conférence autour de Java, s'est tenue la semaine dernière et la blogosphère a déjà allégrement commenté cet évènement. Oracle en a profité pour donner sa feuille de route. Parmi les annonces les plus commentées on notera celles sur JavaFX et sur Java 7/JDK 7.
JavaFX
JavaFX prend une nouvelle direction avec l'abandon de JavaFX Script pour l'utilisation exclusive de l'API Java. Ces changements seront disponibles dans la version 2.0 prévue d'ici mi-2011. Cette orientation permettrait d'avoir plus de ponts vers les langages tournant sur la JVM (groovy, scala…) et pourrait mieux s'intégrer à Swing. Peut-être que cela donnera un nouvel élan à ce framework qui peine un peu à s'imposer.
Java 7 et JDK 7
Le plan, dont nous vous avions parlé, a été définitivement adopté, et le périmètre clairement défini. Annoncé par Mark Reinhold, les nouvelles fonctionnalités peuvent être trouvées ici.
Et aussi
Plus à la marge, quelques liens autour de l'événement :
Replanification de la sortie de Java 7
Tout reste encore hypothétique mais Java 7 pourrait sortir moins en retard que prévu. Initialement planifiée pour septembre 2010 (maintenant!), il semble qu'une implémentation complète de toutes les fonctionnalités de Java 7 ne soit possible avant mi-2012. Mais Mark Reinhold, le responsable chez Oracle de Java 7, a proposé un plan B qui découperait le périmètre de Java 7 en deux. Une première version sortirait mi-2011, qui serait donc la version Java 7 officielle et une deuxième mi-2012, qui deviendrait donc Java 8.
Le périmètre de cette nouvelle version 7 n'est pas encore strictement défini. Seraient retirés du scope:
4 ans après la sortie de Java 6, une certaine attente s'est créée dans la communauté Java. Cette proposition de nouvelle planification avait des allures de sondage auprès des développeurs et à lire les diverses réactions ici et là, il y a de grandes chances qu'Oracle suive le plan B.
Oracle Announces JDK Roadmap for Advancing Java SE
JAVAONE, SAN FRANCISCO – Sept.21, 2010
Oracle Postpones Some Features in JDK 7
Oracle has made some decisions about Java: in order to release JDK 7 in the middle of next year, they have decided to change priorities and specifically, postpone three features: Jigsaw, Lambda and Coin.
From the linked article: "Jigsaw is an effort to make Java more modular, while Project Lambda aims to bring closures to Java, and Project Coin is an effort to make small changes to Java's behavior and syntax."
Although none of these, with the exception of closures, really speak to me (and Java is the language I earn a living with...), my personal feeling is summed up in the first question that came to my mind: why postpone features so that JDK 7 can get out of the pipes fast (i.e. 2011) and still have them in JDK 8 which is planned to be released in 2012?
Maybe that one of the reasons is to not lose too much momentum, but I still don't understand the logic behind the seemingly pressing need to release JDK 7. I don't deny that a 2D and 3D graphics engine would be useful, or that JavaFX bridging "the gap between Java applications and the browser's DOM, where HTML 5 and JavaScript exist" isn't important. I'm just puzzled by the timeline. Less than 18 months between two official JDK releases seems kind of hasty, even in the light of previous release dates. Take a look at JDK 6 and you'll wonder how "small language changes" (see the Oracle webpage linked below) could be unwieldy enough to not be baked in the next release.
In my eyes, Java is just fine as it is since it has always served any purposes I've ever had in my professional projects. I've always felt the language was overhyped for a long time, now it's threatened by the likes of Ruby, Lisp or Smalltalk. I feel like the way Java is either glorified or decried isn't how a language should be treated. I guess you can't fight the tides of progress. But keeping the final product consistent with the feature set until release time looks preferable to removing features, including the drastic change and power Lambda will bring into Java. Especially when the latest release is three months short of being four years old.
The ironic thing is that the "modularization" and "developer productivity" sections still list projects Jigsaw and Coin amongst the key features on Oracle's own website.
Oracle to scale back features for JDK 7
septembre 21, 2010 — Oracle is going with Plan B for JDK 7.
Thomas Kurian, executive vice president of Oracle, took the stage at Oracle OpenWorld and JavaOne on Monday night to remove the uncertainty that has surrounded the Java platform since Oracle closed its acquisition of Sun Microsystems earlier this year.
"I've been at JavaOne since 1997," said Kurian, "but this year is very special for us because it is the first year that Oracle is the steward and responsible for Java. What we want to do today is to make sure every developer is crystal clear on where we see the Java platform evolving."
Plan B calls for the elimination of projects Coin, Jigsaw and Lambda from the JDK 7 release train. This will push forward the completion date of JDK 7 to some time in 2011, and allow the Oracle team to push for JDK 8 in 2012.
JavaOne 2010 Alternative JVM Languages including JavaFX
You probably are already aware that JavaFX Script is no longer to be developed, by Oracle Corporation, beyond JavaFX 1.3.1 release. This is a cost-benefit decision and purely pragmatic business decision. JavaFX is now re-branded to Java API, in order it is JavaFX with Java API. I believe in the long term that Oracle has made a very wise decision. They are looking at the long-tail of computer development, especially in the consumer electronics and portable device space. JavaFX is a client side technology, so they are going aggressively to the TTM (Time-to-market) launch and also answering in one fell swoop two questions that have always been difficult to respond regarding JavaFX. Personal disclosure: yours truly has been aware of Oracle's decision to change JavaFX 2.0 for a few weeks now.
JavaFX Rebooted: The Roadmap For Oracle's Alternative Approach
The big news at JavaOne so far has been the decision to ditch JavaFX Script and use a Java API for creating JavaFX applications instead. The big advantage of this is that JavaFX will be embeddable into Swing through it's embeddable web browser component, breathing some new life into Java desktop applications. It will now be much easier for JavaFX developers to integrate their applications with existing Java business logic, as well as get access to features such as generics and annotations. In these presentation slides from Stephen Chin and Jonathan Giles, you can see how JavaFX can work with alternative languages on the VM such as JRuby, Clojure, Scala and Groovy.
One feature that developers may miss from JavaFX Script is it's binding approach. While no solution is available just yet, according to these slides, there is work being invested into working out how to keep the binding feature alive for JavaFX.
BigMemory Explained a bit...
First you need some context. BigMemory is designed to provide what we call a tiered storage engine.
What it implies is a system that automatically and transparently works behind the cache to keep data as close to the app as possible. You can have a cache with 350GB of data in it, keeping the most frequently used (calculated at runtime) portion in memory with read / write latency under 1 microsecond. You can keep the remaining 350GB in memory but a bit further away from Java heap, and hidden from the Garbage Collector so that it never causes a pause in the JVM while it sits there resident, and that 350GB can be accessed at 100 microseconds. You have seen this before in the hardware. In that sense it is not new.
On-chip cache is faster than RAM and on-chip has multiple levels (L1, L2, L3). And, the caches transparently pull and push data from RAM to the core that needs the data. It works.
- La journée du model driven 2010 est prévue le 25 novembre 2010 à Paris. C'est gratuit mais il est indispensable de s'inscrire sur le site web car le nombre de place est limité : www.mdday.fr.
- OpenOffice change (provisoirement ?) de nom et devient LibreOffice.
- La transition IPV4 vers IPV6 : quel est le plan B ?
- JavaOne 2010 : la plus importante des conférences du monde Java : les annonces majeurs avec une nouvelle sortie du JDK 7 mi 2011 avec une moitié des fonctionnalités prévues et l'autre moitiés repoussées pour le JDK 8 fin 2012, la confirmation de JavaFX 2.0 pour mi 2011, ...
- Un article sur le concept de BigMemory : implémenté par le produit Terracotta.
La journée du « Model Driven » : 25 novembre 2010, Paris
Les principaux acteurs du MDA
Blu Age, Jaxio, Mia-Software, Obeo, Objecteering Software, Objet Direct, Microsoft, Sodius, SoftFluent, W4 vous invitent à la 4ème édition du MD Day, la journée consacrée aux approches « Model Driven .
Une rencontre unique pour échanger, confronter les retours d'expérience et enrichir sa vision des approches du Model-Driven.
Nouveauté cette année : l'agilité sera au cœur des conférences
Principaux temps forts : intervention de Steve Cook, Membre de l'OMG ; table ronde avec des acteurs incontournables de l'agilité comme Laurent Bossavit, Spécialiste des approches Agiles et d'Extreme Programming, Christophe Thibaut, Coach Agile chez OCTO Technology, entre autres.
Outre l'agilité, bon nombre d'autres thèmes seront abordés : modélisation fonctionnelle, génération de code, modernisation du SI, orchestration de processus métier, exécution des modèles, DDD Domain Driven Design, choix entre UML et DSL, ..
Site web :
www.mdday.fr
Le programme :
http://www.mdday.fr/programme.htm
inscription obligatoire sur le site :
register.mdday.fr/seminaire/viewRegisterForm.do
OpenOffice.org divorce et devient LibreOffice
Le couple OpenOffice.org / Oracle a divorcé. La communauté en charge du développement de la suite bureautique open source souhaite voler de ses propres ailes, sans la tutelle d'une entreprise commerciale.
Le développement d'OpenOffice.org (Ooo) était depuis 10 ans réalisé par des volontaires et des entreprises, mais sous l'égide de Sun. Le rachat de ce dernier par Oracle n'a visiblement pas rassuré la communauté Ooo. L'entreprise de Larry
Ellison aurait considéré ce groupe comme faisant davantage "partie du problème que de la solution" a commenté Charles-H. Schulz, l'un des membres d'OOo.
There is no Plan B: why the IPv4-to-IPv6 transition will be ugly
Twenty years ago, the fastest Internet backbone links were 1.5Mbps. Today we argue whether that's a fast enough minimum to connect home users. In 1993, 1.3 million machines were connected to the Internet. By this past summer, that number had risen to 769 million. and this only counts systems that have DNS names. The notion of a computer that is not connected to the Internet is patently absurd these days.
But all of this rapid progress is going to slow in the next few years. The internet will soon be sailing in very rough seas, as it's about to run out of addresses, needing to be gutted and reconfigured for continued growth in the second half of the 2010s and beyond. Originally, the idea was that this upgrade would happen quietly in the background, but over the past few years, it has become clear that the change from the current Internet Protocol version 4, which is quickly running out of addresses, to the new version 6 will be quite a messy affair.
JavaOne 2010
La version 2010 de JavaOne, sans doute la plus grosse conférence autour de Java, s'est tenue la semaine dernière et la blogosphère a déjà allégrement commenté cet évènement. Oracle en a profité pour donner sa feuille de route. Parmi les annonces les plus commentées on notera celles sur JavaFX et sur Java 7/JDK 7.
JavaFX
JavaFX prend une nouvelle direction avec l'abandon de JavaFX Script pour l'utilisation exclusive de l'API Java. Ces changements seront disponibles dans la version 2.0 prévue d'ici mi-2011. Cette orientation permettrait d'avoir plus de ponts vers les langages tournant sur la JVM (groovy, scala…) et pourrait mieux s'intégrer à Swing. Peut-être que cela donnera un nouvel élan à ce framework qui peine un peu à s'imposer.
Java 7 et JDK 7
Le plan, dont nous vous avions parlé, a été définitivement adopté, et le périmètre clairement défini. Annoncé par Mark Reinhold, les nouvelles fonctionnalités peuvent être trouvées ici.
Et aussi
Plus à la marge, quelques liens autour de l'événement :
- Durant son passage à JavaOne, Stephen Colebourne s'est amusé à faire un petit sondage sur les exceptions vérifiées et donne son point de vue
- John Coomes et Tony Printezis ont fait une présentation sur les mythes entourant le garbage collector
- une application pour visualiser les différents concepts de l'API concurrent, très didactique
- James Gosling s'est expliqué sur son départ d'Oracle
Replanification de la sortie de Java 7
Tout reste encore hypothétique mais Java 7 pourrait sortir moins en retard que prévu. Initialement planifiée pour septembre 2010 (maintenant!), il semble qu'une implémentation complète de toutes les fonctionnalités de Java 7 ne soit possible avant mi-2012. Mais Mark Reinhold, le responsable chez Oracle de Java 7, a proposé un plan B qui découperait le périmètre de Java 7 en deux. Une première version sortirait mi-2011, qui serait donc la version Java 7 officielle et une deuxième mi-2012, qui deviendrait donc Java 8.
Le périmètre de cette nouvelle version 7 n'est pas encore strictement défini. Seraient retirés du scope:
- le projet lambda
- le projet jigsaw (modularisation de la jvm)
- une partie non définie du projet Coin
4 ans après la sortie de Java 6, une certaine attente s'est créée dans la communauté Java. Cette proposition de nouvelle planification avait des allures de sondage auprès des développeurs et à lire les diverses réactions ici et là, il y a de grandes chances qu'Oracle suive le plan B.
Oracle Announces JDK Roadmap for Advancing Java SE
JAVAONE, SAN FRANCISCO – Sept.21, 2010
Oracle Postpones Some Features in JDK 7
Oracle has made some decisions about Java: in order to release JDK 7 in the middle of next year, they have decided to change priorities and specifically, postpone three features: Jigsaw, Lambda and Coin.
From the linked article: "Jigsaw is an effort to make Java more modular, while Project Lambda aims to bring closures to Java, and Project Coin is an effort to make small changes to Java's behavior and syntax."
Although none of these, with the exception of closures, really speak to me (and Java is the language I earn a living with...), my personal feeling is summed up in the first question that came to my mind: why postpone features so that JDK 7 can get out of the pipes fast (i.e. 2011) and still have them in JDK 8 which is planned to be released in 2012?
Maybe that one of the reasons is to not lose too much momentum, but I still don't understand the logic behind the seemingly pressing need to release JDK 7. I don't deny that a 2D and 3D graphics engine would be useful, or that JavaFX bridging "the gap between Java applications and the browser's DOM, where HTML 5 and JavaScript exist" isn't important. I'm just puzzled by the timeline. Less than 18 months between two official JDK releases seems kind of hasty, even in the light of previous release dates. Take a look at JDK 6 and you'll wonder how "small language changes" (see the Oracle webpage linked below) could be unwieldy enough to not be baked in the next release.
In my eyes, Java is just fine as it is since it has always served any purposes I've ever had in my professional projects. I've always felt the language was overhyped for a long time, now it's threatened by the likes of Ruby, Lisp or Smalltalk. I feel like the way Java is either glorified or decried isn't how a language should be treated. I guess you can't fight the tides of progress. But keeping the final product consistent with the feature set until release time looks preferable to removing features, including the drastic change and power Lambda will bring into Java. Especially when the latest release is three months short of being four years old.
The ironic thing is that the "modularization" and "developer productivity" sections still list projects Jigsaw and Coin amongst the key features on Oracle's own website.
Oracle to scale back features for JDK 7
septembre 21, 2010 — Oracle is going with Plan B for JDK 7.
Thomas Kurian, executive vice president of Oracle, took the stage at Oracle OpenWorld and JavaOne on Monday night to remove the uncertainty that has surrounded the Java platform since Oracle closed its acquisition of Sun Microsystems earlier this year.
"I've been at JavaOne since 1997," said Kurian, "but this year is very special for us because it is the first year that Oracle is the steward and responsible for Java. What we want to do today is to make sure every developer is crystal clear on where we see the Java platform evolving."
Plan B calls for the elimination of projects Coin, Jigsaw and Lambda from the JDK 7 release train. This will push forward the completion date of JDK 7 to some time in 2011, and allow the Oracle team to push for JDK 8 in 2012.
JavaOne 2010 Alternative JVM Languages including JavaFX
You probably are already aware that JavaFX Script is no longer to be developed, by Oracle Corporation, beyond JavaFX 1.3.1 release. This is a cost-benefit decision and purely pragmatic business decision. JavaFX is now re-branded to Java API, in order it is JavaFX with Java API. I believe in the long term that Oracle has made a very wise decision. They are looking at the long-tail of computer development, especially in the consumer electronics and portable device space. JavaFX is a client side technology, so they are going aggressively to the TTM (Time-to-market) launch and also answering in one fell swoop two questions that have always been difficult to respond regarding JavaFX. Personal disclosure: yours truly has been aware of Oracle's decision to change JavaFX 2.0 for a few weeks now.
JavaFX Rebooted: The Roadmap For Oracle's Alternative Approach
The big news at JavaOne so far has been the decision to ditch JavaFX Script and use a Java API for creating JavaFX applications instead. The big advantage of this is that JavaFX will be embeddable into Swing through it's embeddable web browser component, breathing some new life into Java desktop applications. It will now be much easier for JavaFX developers to integrate their applications with existing Java business logic, as well as get access to features such as generics and annotations. In these presentation slides from Stephen Chin and Jonathan Giles, you can see how JavaFX can work with alternative languages on the VM such as JRuby, Clojure, Scala and Groovy.
One feature that developers may miss from JavaFX Script is it's binding approach. While no solution is available just yet, according to these slides, there is work being invested into working out how to keep the binding feature alive for JavaFX.
BigMemory Explained a bit...
First you need some context. BigMemory is designed to provide what we call a tiered storage engine.
What it implies is a system that automatically and transparently works behind the cache to keep data as close to the app as possible. You can have a cache with 350GB of data in it, keeping the most frequently used (calculated at runtime) portion in memory with read / write latency under 1 microsecond. You can keep the remaining 350GB in memory but a bit further away from Java heap, and hidden from the Garbage Collector so that it never causes a pause in the JVM while it sits there resident, and that 350GB can be accessed at 100 microseconds. You have seen this before in the hardware. In that sense it is not new.
On-chip cache is faster than RAM and on-chip has multiple levels (L1, L2, L3). And, the caches transparently pull and push data from RAM to the core that needs the data. It works.
Aucun commentaire:
Enregistrer un commentaire