Pour le bulletin de cette semaine, je vous propose les sujets suivants :
Je vous souhaite également, pour vous et vos proches, de passer de bonnes fêtes et les meilleurs vœux pour la prochaine année 2011.
Bonne lecture.
Devoxx – L'avenir de Java
La keynote de Mark Reinhold, Chief Architect de la plate-forme Java chez Oracle, était particulièrement attendue après une actualité très riche sur le JDK ces derniers mois. L'année dernière, l'annonce d'un nouveau délai pour la sortie de JDK 7, afin de permettre la ré-intégration des closures, avait provoqué la surprise. L'été arrivant, la communauté se rendait alors compte que le planning initial prévoyant un JDK 7 features complete pour juin était déjà dépassé et irréaliste. Quelques mois plus tard, Mark Reinhold annonçait sur son blog un "plan B" : on ne conserverait alors dans JDK 7 que les fonctionnalités déjà implémentées pour repousser celles qui sont encore en cours d'élaboration, telles que les closures ou la modularité, au JDK 8. Plus récemment l'actualité était marquée par l'annonce de nouveaux entrants dans le projet OpenJDK : IBM dans un premier temps, s'étant résigné à mutualiser ses efforts de développements avec Oracle, et Apple qui après l'annonce de l'arrêt du support de Java dans Mac OS X avait décidé de léguer les développements spécifiques à son OS au projet OpenJDK. Dans ce contexte rempli de rebondissements et d'incertitudes, Mark Reinhold a apporté quelques clarifications et une visibilité appréciable sur l'avenir de Java.
JSRs for Java 7 and Java 8 Approved
The results of the recent Java JSRs are in, and all have passed with all but Apache voting consistently against them. Google and Tim Peierls voted
against the Java SE 7 and Java SE 8 JSRs, supporting the ongoing licensing issues and field-of-use restrictions for the TCK.
Project Coin, JSR 334, passed with 13 votes to 1 (and 1 abstention)
Project Lambda, JSR 335, passed with 13 votes to 1 (and 1 abstention)
Java SE 7, JSR 336, passed with 12 votes to 3
Java SE 8, JSR 337, passed with 12 votes to 3
Spring 3.0 AOP Advice
Abbrevation of Spring AOP is Aspect-oriented programming, Action taken by an aspect at a particular join point is known as Spring AOP advice. To say simple, Spring models an advise as an interceptor and maintains a chain of interceptors by adding functionalities before or after the method execution. In this article, the various types of AOP advice in Spring 3.0 is explained in an elegant way. The types are,
1. Before Advice
2. After Returning Advice
3. After Throwing Advice
4. Around Advice
How To Pay Down Technical Debt
What is technical debt? Ward Cunningham coined the term "technical debt" to refer to an obligation that an organization takes on when it decreases the quality of its code base in order to meet short-term goals. Bringing code quality back up invariably costs more to do later on than it would have if quality had been addressed immediately. This extra cost represents the "interest" on the technical debt.
HTML5 in the browser: Canvas, video, audio, and graphics
The five characters HTML5 are now an established buzzword, found everywhere on the Web and often given top billing in slides, feature lists, and other places where terms du jour congregate. Non programmers who must either manage or work with programmers are even beginning to pick up the term. Just two days ago, someone who can't manage a TV remote explained that he was sure his company's Web presence would be much better because they were using HTML5.
The Road Ahead for UML
Ivar Jacobson is founder and CTO of Ivar Jacobson International and co-developer of UML. Steve Cook is a software architect at Microsoft and represents Microsoft at the OMG. More than 12 years have passed since the Unified Modeling Language (UML), became a standard. During these years opinions of UML have varied between delight and distaste. In this article, we discuss the deficiencies of the current UML specification and propose how to make it agile, leaner, smarter, and more flexible -- in short, how to prepare it for the future so that users can be confident that their investments in UML today will increase in value going forward.
At the beginning of the '90s there were 26 published methods on object-orientation, ...
Introduction to OpenCL
Using a GPU for computational workloads is not a new concept. The first
work in this area dates back to academic research in 2003, but it took the
advent of unified shaders in the DX10 generation for GPU computing to be a
plausible future. Around that time, Nvidia and ATI began releasing proprietary
compute APIs for their graphics processors, and a number of companies
were working on tools to leverage GPUs and other alternative architectures.
The landscape back then was incredibly fragmented and almost every option
required a proprietary solution – either software, hardware or both. Some of
the engineers at Apple looked at the situation and decided that GPU
computing had potential – but they wanted a standard API that would let them
write code and run on many different hardware platforms. It was clear that
Microsoft would eventually create one for Windows (ultimately
DirectCompute), but what about Linux, and OS X? Thus an internal project
was born, that would eventually become OpenCL.
- A la conférence Devoxx : keynote sur l'avenir de Java par Mark Reinhold (Oracle).
- Le JCP (Java Community Process) approuve les spécifications du JDK 7 et du JDK 8 : 12 votes pour, trois votes contre.
- La programmation par aspect dans Spring 3.0 : les intercepteurs.
- Comment payer la dette technique.
- Le HTML5 et les cinq fonctionnalités multi-média.
- Les 12 ans d'UML : bilan.
- Introduction d'OpenCL : la programmation du processeur graphique (le GPU).
Je vous souhaite également, pour vous et vos proches, de passer de bonnes fêtes et les meilleurs vœux pour la prochaine année 2011.
Bonne lecture.
Devoxx – L'avenir de Java
La keynote de Mark Reinhold, Chief Architect de la plate-forme Java chez Oracle, était particulièrement attendue après une actualité très riche sur le JDK ces derniers mois. L'année dernière, l'annonce d'un nouveau délai pour la sortie de JDK 7, afin de permettre la ré-intégration des closures, avait provoqué la surprise. L'été arrivant, la communauté se rendait alors compte que le planning initial prévoyant un JDK 7 features complete pour juin était déjà dépassé et irréaliste. Quelques mois plus tard, Mark Reinhold annonçait sur son blog un "plan B" : on ne conserverait alors dans JDK 7 que les fonctionnalités déjà implémentées pour repousser celles qui sont encore en cours d'élaboration, telles que les closures ou la modularité, au JDK 8. Plus récemment l'actualité était marquée par l'annonce de nouveaux entrants dans le projet OpenJDK : IBM dans un premier temps, s'étant résigné à mutualiser ses efforts de développements avec Oracle, et Apple qui après l'annonce de l'arrêt du support de Java dans Mac OS X avait décidé de léguer les développements spécifiques à son OS au projet OpenJDK. Dans ce contexte rempli de rebondissements et d'incertitudes, Mark Reinhold a apporté quelques clarifications et une visibilité appréciable sur l'avenir de Java.
JSRs for Java 7 and Java 8 Approved
The results of the recent Java JSRs are in, and all have passed with all but Apache voting consistently against them. Google and Tim Peierls voted
against the Java SE 7 and Java SE 8 JSRs, supporting the ongoing licensing issues and field-of-use restrictions for the TCK.
Project Coin, JSR 334, passed with 13 votes to 1 (and 1 abstention)
Project Lambda, JSR 335, passed with 13 votes to 1 (and 1 abstention)
Java SE 7, JSR 336, passed with 12 votes to 3
Java SE 8, JSR 337, passed with 12 votes to 3
Spring 3.0 AOP Advice
Abbrevation of Spring AOP is Aspect-oriented programming, Action taken by an aspect at a particular join point is known as Spring AOP advice. To say simple, Spring models an advise as an interceptor and maintains a chain of interceptors by adding functionalities before or after the method execution. In this article, the various types of AOP advice in Spring 3.0 is explained in an elegant way. The types are,
1. Before Advice
2. After Returning Advice
3. After Throwing Advice
4. Around Advice
How To Pay Down Technical Debt
What is technical debt? Ward Cunningham coined the term "technical debt" to refer to an obligation that an organization takes on when it decreases the quality of its code base in order to meet short-term goals. Bringing code quality back up invariably costs more to do later on than it would have if quality had been addressed immediately. This extra cost represents the "interest" on the technical debt.
HTML5 in the browser: Canvas, video, audio, and graphics
The five characters HTML5 are now an established buzzword, found everywhere on the Web and often given top billing in slides, feature lists, and other places where terms du jour congregate. Non programmers who must either manage or work with programmers are even beginning to pick up the term. Just two days ago, someone who can't manage a TV remote explained that he was sure his company's Web presence would be much better because they were using HTML5.
The Road Ahead for UML
Ivar Jacobson is founder and CTO of Ivar Jacobson International and co-developer of UML. Steve Cook is a software architect at Microsoft and represents Microsoft at the OMG. More than 12 years have passed since the Unified Modeling Language (UML), became a standard. During these years opinions of UML have varied between delight and distaste. In this article, we discuss the deficiencies of the current UML specification and propose how to make it agile, leaner, smarter, and more flexible -- in short, how to prepare it for the future so that users can be confident that their investments in UML today will increase in value going forward.
At the beginning of the '90s there were 26 published methods on object-orientation, ...
Introduction to OpenCL
Using a GPU for computational workloads is not a new concept. The first
work in this area dates back to academic research in 2003, but it took the
advent of unified shaders in the DX10 generation for GPU computing to be a
plausible future. Around that time, Nvidia and ATI began releasing proprietary
compute APIs for their graphics processors, and a number of companies
were working on tools to leverage GPUs and other alternative architectures.
The landscape back then was incredibly fragmented and almost every option
required a proprietary solution – either software, hardware or both. Some of
the engineers at Apple looked at the situation and decided that GPU
computing had potential – but they wanted a standard API that would let them
write code and run on many different hardware platforms. It was clear that
Microsoft would eventually create one for Windows (ultimately
DirectCompute), but what about Linux, and OS X? Thus an internal project
was born, that would eventually become OpenCL.
Aucun commentaire:
Enregistrer un commentaire