• Je viens de passer le week-end à Anglet. Pour les parigots pur-porc ignorants de la côte atlantique, c'est entre Bayonne et Biarritz... Les 40 ans de mon plus vieil ami David ont été un succès énorme. La fête était sympa, sympa comme ne peuvent presque pas l'être les fiestas en région parisienne. Ambiance super-décontractée, bouffe locale exceptionnelle, avec cette élégance cool et pas endimanchée pour un sou commune à tout le Sud-Ouest sauf certains quartiers de Bordeaux. Quand on revient de là-bas, on ne peut se faire qu'une seule réflexion : les ploucs sont en région parisienne.
  • Dans la salle d'attente d'Orly vendredi soir, j'ai été le seul à reconnaître Louis Gallois assis sagement en face de moi, dans l'attente du même vol. J'ai apprécié le fait que ce type qui pourrait se pavaner en jet privé soit en jean-polo et vol régulier avec madame. Bon, place 1C (couloir) mais quand même.
  • World Wide Web Foundation launched... In the meantime W3C AC-Reps have other stuff on the radar, and urgent stuff.
  • CSS transformations in Gecko.... The 'transform' property was proposed by David Hyatt a year ago. The 7th of september 2007 to be more precise. But some transformations like rotations were originally proposed to the CSS WG ten years before through a suggested 'rotate' property ! At the same time, Microsoft came up with its filter property. The rotate property was rejected for super-mega-hyper serious and blocking reasons about the bounding box raised by all browser implementors. It's funny to see the same browser implementors today find no issue at all implementing rotations in CSS. Just one minor nit for Web designers, though : we lost ten years.
  • Tristan loves Ubiquity. I love the feature. I find the UI metaphor and the keyboard-based thing just awful and incredibly geeky. To me, it has a taste of "call -16304" to enter hi-res graphics mode on an apple ][. From a UI's perspective, Ubiquity is IMHO a "please the geeks" extension to Firefox. Sorry to be the only disruptive echo in the praise logorrhea : keep the feature, forget about the keyboard as much as you can.
  • UPS notified me they're going to deliver a 2.5 kilograms box of t-shirts and mozilla stuff at my place (re. Extend Firefox 3 Contest). Thanks Mozilla !
  • I read "Two thousand twenty two" by Jeff Croft. I can't tell how much I disagree. I can't tell how much this attitude is the wrong way. I can't tell but I can show. I just found this lovely chunk in a web page :
    .warningNew {
    -webkit-border-image: url(star_border.png) 15 15 15 15 round round;
    -moz-border-image: url(star_border.png) 15 15 15 15 round round;
    }

    And I strongly disagree with James Graham when he says that finishing HTML5 in 2022 has no importance at all. But it's not the first time James and I don't share the same vision of things. When you deal with something ubiquitous like HTML and know the press is going sooner or later to look at that 2022 deadline (hey make it directly 2032, I'll be retired !!!) more carefully, it's much better to remain silent than to say "2022". There's another point that has to be made : I have no idea what means "finished" for a standard. I know what means "released". But a spec is never finished. Or it's "finished" when it's really finished, and I mean "dead" or "obsolete" here. We're humans and humans do mistakes. HTML 5 will be just like any other spec in any other domain, it will contain errors and HTML5 will have to deal with errata. HTML 4 did not deal with errata ONLY because of the bloody stupid attitude of the XHTML2 Working Group that decided, against all technological and strategic wisdom, not to deal with HTML4 errata. And we paid the big price for that big mistake.

    Let me show the problem from another perspective : the LHC is a 25 years project. And HTML 5 is a18 years project ???? There is something seriously rotten here.