Bonjour,
Well... on efface tout et on recommence depuis le début:
* first one:
Mary Jo Foley a écrit :
I've heard the next version of Windows is not going to be Windows 9. Instead, I've heard from a couple of my contacts that some kind of an update is coming next year. The Windows release codenamed "Blue" -- mentioned by Win8China last week -- is likely the codename of this interim release, my contacts claim.
I'm not clear if Blue is simply what we in the Windows world typically call a service pack, which is a rollup of fixes and updates. Or maybe Blue is more of a feature pack, which would/could include be a rollup of fixes plus some new features.
And if we'll see Blue materializes in the summer of 2013, as I've heard from some of my contacts....
* second one:
Paul Thurrott a écrit :
Speaking of changing Windows 8, one of the dirty little secrets about Microsoft’s next OS is that—surprise—it’s not really done. See, those Metro experiences that we’re supposed to call something else are very much a 1.0 product, and the state they’re shipping in this year is very basic indeed... And for the next few years at least, we’re going to be dealing with a lot of updating.
The question, however, is what form these updates will take. (Service Packs? Feature Packs? Windows Updates?) Mr. Sinofsky announced this change to employees about a month ago in a heavily-protected internal memo that I’m still trying to get my hands on. But based on the bits I’ve heard about, everything is changing.
Donc on part du postulat que Windows 8 est inachevé. Ensuite on échafaude des hypothèses: qu'a donc en tête Steven Sinofsky, quel avenir envisage t'il exactement pour Windows ?
Mary Jo se base sur ses contacts et emprunte la piste d'une "Interim Release" (ou "Interim Build" selon historique Vista/Seven), codenamed Blue, peut-être courant 2013.
Mais d'après Paul, il y a une théorie crédible selon laquelle l'objectif serait de pousser "Metro", le mener à une maturité suffisante afin de pouvoir balayer et reléguer l'interface Desktop vieillissante au rang de mode de maintenance.
Et ce fameux mémo interne sous très haute protection qui suppose t'on poserait les principes de ces changements injectés à coups de paquets de mises à jour étalés sur plusieurs années.
Si le contenu dudit mémo était rendu public, on peut se demander quelles en seraient les conséquences, y compris pour l'auteur de la fuite.
Canouna a juste balancer un "no comment"...
@+
