Warning Bill, the lizard still bites

Entries feed - Comments feed

Wednesday 20 June 2012

BlueGriffon EPUB Edition beta1

I am happy and proud to let you know I have in front of me a first beta version of my new Gecko-based ebook editor, BlueGriffon EPUB Edition. You'll find the whole story on the BlueGriffon blog.

Thursday 14 June 2012


I took a few minutes to hack a helper add-on for planet.mozilla.org and planet.mozilla.org/projects. It adds folding/unfolding to all feed entries and all are folded by default, leaving only the titles visible. It helps me a lot so if you feel it can help you too, here it is. Enjoy! Provided "as is", certainly not optimized, you've been warned.

Friday 27 April 2012


  1. open TV after dinner to watch the news
  2. switch to channel 3, french national TV for their news report that started a few minutes ago
  3. immediately, see Tristan Nitot appear on screen !

Tristan, you're the best... I think you even beat Tantek :-)

Tuesday 17 April 2012

So long Cédric...

Cédric Corazza, a core pillar of the french community, leaves the world of Mozilla after nine years with us :-( So long Cédric, et merci pour tous les poissons.

Monday 9 April 2012

Freerecord 5.01

Free.fr ayant légèrement modifié sa console utilisateurs, mon extension Freerecord de programmation d'enregistrements télé ne fonctionnait plus. Je viens de la mettre à jour vers la 5.01. Malheureusement, suite à un crash système majeur, j'ai perdu la clé privée me permettant les mises à jour automatiques de Freerecord. Firefox ne peut donc pas proposer de mise à jour automatique de la 5.0 à cette 5.01 et il vous faut la recharger et la réinstaller ; cela refonctionnera pour les versions suivantes. Désolé...

Thursday 8 March 2012


(Note: this article did not originally appear on planet ; but given the incredibly violent reactions to Gerv's article I read, I changed its category)

Associating Gervase Markham and the words "hate speech" or "a particular group of people are not human" are very clear indicators that the author (Tim Chevalier) of these words doesn't know our Gerv, should urgently cool down, vent his anger on something else or focus his energy on treating his own paranoia. And Tim is not the only one who should cool down. The reactions to Gerv's post are far too violent.

Associating Gervase Markham and the words "we’ve fired people who made bigoted remarks at work before, and we’ll do it again" seems to me a rather violent attack on Gervase's UK constitutional rights granted to all UK citizens physically in the UK to say what is legal is the UK on their UK blog. And even a US employer can't go against that inside the European Union. Associating Gerv and these words is a threat, and that threat is no better than the imaginary hate it calls against. That threat is, at least to me, unacceptable and has nothing to do with the Mozillian spirit.

Years ago, someone left hate messages on Gerv's blog abusing my identity. Gerv did the right thing : he pinged me instead of replying instantly with public hate himself. Why is so hard to do the same in the current case and solve the issue as ADULTS instead of draggling Gerv backwards and forwards in the mud?

Planet.mozilla.org syndicates blogs without filter. Fix planet, but stop harassing Gerv. Period. His blog, his web site, his freedom of speech, with perfectly legal words as a UK citizen. I don't agree with Gerv here, but I fail 100% seeing hate or humanity denial in his prose. And associating his own prose to Mozilla-the-corporation-and-the-foundation only because it appeared on an unfiltered pmo seems to me strict political correctness.

Today, on pmo, there's a blog article titled "Freelancing". It has nothing to do with Mozilla, strictly saying. It could be understood as an ad for the author. Syndicated too on Mozilla resources ; interestingly, nobody reacted to that one. The Mozilla Community is global? Show it. Show you're able to deal with other cultures, other law systems, other opinions. Debate. But don't silence people. Silencing legal opinions is dictatorship.

Anyway, I also wanted to tell my support to pmo peers ; staying onboard and keeping the boat sailing in the middle of such a ridiculous storm is not funny, not a nice moment. Thanks for doing your duty and remaining a voice of sanity, guys. Seriously.

Saturday 25 February 2012

Hoodies in Paris

I was wearing my black Firefox hoodie yesterday, walking in the streets of Paris with my kids and my dad going to a restaurant for my birthday when we had the big surprise to see another black Firefox hoodie walking in front of us ! Opened my jacket to show mine, Ooooh, Aaaaaah :-) Two Mozillians from the B2G team, visiting the Mozilla Paris offices and spending some time in the nice Marais. It was really fun to meet only because we were proudly wearing our Firefox hoodie :-) Small world, after all. Thanks for that, Mozilla !

Thursday 22 December 2011

Displaying standalone images on dark background

That's in Firefox recent builds. Nice. In particular for dark images with a lot of alpha transparency :-( Now click on the image below to see it standalone. I find the result incredibly disturbing in terms of contrasts. That will probably be a severe accessibility issue for contrast-impaired people. Why was such a change done instead of adding a new checkbox preference to the Content panel of the preferences window "View images over dark background", unchecked by default?

BlueGriffon logo over dark background

Wednesday 21 December 2011

Folding tags in CodeMirror

CodeMirror offers a very convenient and light piece of code to fold code between curly braces. Very cool for the JavaScript editor into my codemirror2-based branch of BlueGriffon but not enough for the Source view of BlueGriffon itself. I needed to fold tags and not code so I wrote my own codemirror "plugin" for that. It's available here, licensing terms are included in the file. Enjoy !

Source view with one folded element

Friday 16 December 2011

Bespin, Skywriter, Ace and BlueGriffon

Exactly two years ago almost to the day, BlueGriffon started using Bespin for its source editor.

Two years and two name changes later, not only the project has drastically changed from its original codebase but the documentation for the project is still almost non-existent; lack of doc is already painful for a project like mine, a wysiwyg standalone editor, but it's awful for an embeddable project like Ace.

The complexity of the code and its architecture, it's monstruous size, the crazyness of themes in CSS themselves contained in JS and more make my every day's life with Ace more and more difficult every day.

I am pondering switching to another source code editor because of:

  1. readability of the code; using Require.js all over the place helps the developer, rarely the user. The other embeddable editor I'm currently looking at is incredibly more readable than Ace. When I want to hack Ace, I'm totally lost and I never know if the code I'm writing will be correctly exposed to the external world. Even worse, I never know if a given function I was planning to use is exposed to me or how.
  2. size of the code; the other embeddable editor I'm currently looking at is 4 times smaller than Ace... Sorry, but yeah, size matters.
  3. theming is too complex for what it's worth in Ace. I want CSS and CSS only, like in any good web page.
  4. speed - and I agree Ace is fast - is not an excuse. The other embeddable editor I'm currently looking at has no problem whatsoever dealing with a 35,000 lines javascript file.
  5. embedding a grammar inside another one, and html documents can contain scripts and css while html file can also contain php, is vital to me. Doing that in Ace is, to say the least, totally cryptic to me.
  6. autocompletion should not be complex to add. With Ace, it is complex. A good autocompletion for html or CSS should not be more than roughly 30 lines of very light JavaScript.

I understand this is not a positive message, but I wanted to share my concerns with you if that can help the project. Even if I may stop using it in the very near future, I wish Ace all the best.

Monday 5 December 2011

Customize Firefox keyboard shortcuts

I adapted my code from BlueGriffon to Firefox this morning. Apparently Tim Taubert independently had the same idea - and also the same UI - a while ago. I promise I did not know about his code when I started mine. Anyway, you can find my XPI for Firefox 5+ here. Warning, in the case of Firefox, it's still highly experimental, can lead to severe issues because of bug 707633. Restart Firefox after installation and you'll find a new panel in the Preferences window.

(if you experience long delay between the click on the XPI link above and the "Install add-on" dialog, that's bug 657581)

Thursday 13 October 2011


Disruptive Innovations, home for BlueGriffon, Nvu and so many other projects, is 8 years old today :-) So I spent more time in my own company than in any other company I worked for... What a ride !

Tuesday 11 October 2011

How I got involved with Mozilla

This is a response to David Boswell’s post.

Back in 1998, I was already a member of the W3C CSS Working Group (on behalf of EDF, Électricité de France) and Peter Linss, my current co-chair in the same Group, was an employee of Netscape. Peter wanted to hire me at Netscape but it was unsuccessful at that time because of a hire freeze... Two years later, I had left EDF to become the CTO of Amazon France and later Halogen and Netscape employee (and good friend) Pierre Saslawsky pinged me during a CSS WG meeting (was it in May in Sophia or August in Oslo...) and asked me if I was available. I answered positively. Back in Mountain View, he made a referral about me and Netscape's HR called me a few weeks later. Netscape paid me a trip to Mountain View for an interview. But because I said multiple teams looked interesting to me (if I recall correctly: Layout, Editor, Mail and IM), I ended up spending 3 whole days in interviews with all these teams. Layout because I loved it, Editor because I had a lot of experience about that, Mail because I implemented one of the very first MIME-compliant Mail User Agents, and IM because I found it really interesting. Met Vidur, Waldemar, Beppe, Scott, Jst, and many others. My interview with Beth Epperson (aka Beppe) went really well; she was managing the editor team and told me later she left the room telling everyone "I want him, period" :-)

The last day, the CTO Clayton Lewis told me the interviews were positive. He asked me then "Do you want to relocate to the Bay Area or stay in Paris?". I replied "Stay in Paris if possible". He answered "Well, I usually prefer having my teams around me but if we cannot do it, who can do it... So let's do that: six months in Paris in Netscape offices and if working remotely with us does not work, you relocate to MV". I accepted with true joy.

I started working for Netscape the 1st of november 2000, starting with... a CSS WG meeting hosted by Pierre Saslawsky in San Francisco. I will always remember the "Too close to call" messages during election night, spent at Pierre's place. Arrived in MV right after the meeting. Welcomed by Carrie Friedberg to learn a Netscape 6 barbecue party was on its way :-) Got my lizard badge (a pride you can't imagine!), my computer, my cubicle in less than an hour and spent the whole month in building 21, learning a lot, really a lot from Joe Francis, Kin Blas, Akkana Peck, Beth, Michael Judge, Charles Manske and few others. I left building 21 the first day with a load of new mostly black t-shirts, a Netscape 6 jacket and an enormous smile on my face.

I fixed my first bug after a few days only. Something in the Style Engine IIRC. Then lots of bugs in the editor and a few in the Style Engine. Kin Blas vouched for me for CVS write access. And I flew back to Paris at the end of november to work from Netscape offices until 02-aug-2003, after the final 15-jul-2003 layoffs. Formally left the Netscape payroll 02-nov-2003 but launched Disruptive Innovations 13-oct-2003 and we're still here 8 years later, still working full time on Mozilla and Web Standards. Yay !

And you?

Wednesday 5 October 2011

a HTML Spaghetti Western: The Serializer, The Parser and The Ugly Blank Lines

Our content serializer has a lot of flaws. I could mention wrapping that often does not work as expected and should not wrap asian scripts, raw mode that is not really raw, and more. But one of the most painful bugs is a bug related to blank lines suddenly appearing in the serialization of HTML documents. To experience that bug with a modern gecko-based editor, launch BlueGriffon, click on the drop-down arrow of the New button and create a transitional HTML4 document. Switch to source view and back to wysiwyg a few times.

  1. there is an extra blank line appearing between <head> and <meta> each time you switch to Source !
  2. there are unexplainable blank lines after the paragraph

These are two different problems.... The latter one is weird and painful: if I load this trivial empty HTML4 document into Firefox and inspect it using the DOM Inspector or Firebug, I see a text node erroneously (in fact, it's erroneous for SGML parsing that applies to HTML 4, but that's the html5 parsing model) containing multiple CRs... In fact, the serializer here is not buggy, there are really multiple CRs after the end of the paragraph element. In fact all the nodes between just after </body> and the end of the document are appended to the body element in the DOM; adjacent text nodes are concatenated. So the serializer is not buggy here, it really sees blank lines. I will hack BlueGriffon source view to work around that.

<hsivonen> glazou: that's intentional, spec compliant and by design
<hsivonen> glazou: sucks for editors. makes sense for all other classes of products ingesting HTML
<hsivonen> glazou: this significantly simplifies dealing with random cruft after </body>
<hsivonen> glazou: WebKit has done this for years with great success
<hsivonen> glazou: this is the Web
<aja> "leave all sense of logic at the door" :-)

If I understand perfectly the rationale behind that parsing choice for browsers, it just sucks for non-browsers. It's a pain for editors, filters, all tools having to deal with source or exact DOM representation of the document instance. A text node can live in the DOM after the body or even the html elements. That's how we can have a xml-stylesheet PI or comments living before the root of the document...

I think the parsing model should be changed here, or adapted to be more precise : extra nodes after the body element should be appended to the body element if and only if they are not all blank (matching /^\s*$/) text nodes. If they are all blank text nodes, they remain in place and are ignored by the UAs or are deleted from the DOM. That would preserve the behaviour hsivonen needs above and would help a lot editors and transformation tools. A good compromise, in my humble opinion. At least a better one than the current one.

The head/meta problem is a weakness of Gecko's serializer: the mMayIgnoreLineBreakSequence attribute is not correctly used in nsHTMLContentSerializer and nsXMLContentSerializer. In particular, nsXMLContentSerializer::AppendToString should detect if the string to append contains CR or LF and contains only whitespaces (à la \s). If both are true, then mMayIgnoreLineBreakSequence should be set to true. Of course, AppendNewLineToString() should return without proceeding if mMayIgnoreLineBreakSequence is true, and AppendIndentation should probably not set it back to false. A few other spots have to be modified too but all in all it should be doable. I hope there won't be bad side effects for instance on some specific elements like pre. Stay tuned.

Wednesday 27 July 2011

Your page in 3D

mozilla.org in 3DTilt is cool. Very cool. But I almost see it as a debugging tool and I wish the links were clickable, Firebug or DOMI could work. So I did what I always do in such a case, what I did long ago with Small Screen Rendering: I used CSS :-) It's less powerful since the 3D is not dynamic but as a debugging tool, it's probably more useful.

Take a web page, any web page, and add this stylesheet to the document. Reload in Firefox.

body {
-moz-transform: skew(-6deg, 0deg);
-moz-transform-origin: center center;

*:not(body):not(html):not(a):not(img):not(span) { -moz-transform: translate(0px, 6px); -moz-border-bottom-colors: gray silver silver silver silver gray; border-bottom: 6px silver solid; -moz-border-right-colors: gray silver silver gray; border-right: 4px transparent solid; border-top: 1px gray solid; border-left: 1px gray solid; }

Note: you can use this very convenient bookmarklet: Test Styles. Just drop it onto your bookmarks toolbar and use it.

Update: of course, once we have 3D Transforms, it'll be even cleaner and simpler.

Friday 22 July 2011

Firefox, BlueGriffon and OS X Lion

One thing I immediately missed under OS X Lion was the ability to scroll to the top or bottom of a document with three fingers. Since I browse a lot of long documents, for instance W3C specs, I really needed it back. Open OS X Preferences, show the trackpad panel, switch to the last tab, and select "4 fingers" for the Mission Control and Exposé trackpad shortcuts. Then your usual three-fingers scrolling gestures still work in Firefox.

Far beyond that, I have a question related to the new NSDocument features if you're a mac Mozillian: how could I enable the versioning and autosave features in BlueGriffon?

Note: I tried switching to the new scrolling beheviour of Lion. I really tried. Just could not. I switched back to the Snow Leopard behaviour unchecking the first checkbox in the second tab of the trackpad preferences panel...

Monday 18 July 2011

Suggestion of changes to the add-ons manager

it's everywhere. Add-ons broken (hear disabled) by faster updates of Firefox are a pain for users. I think Mozilla could prevent this implementing the rather simple following rules:

  • if an add-on's maxVersion does not match any more Firefox's version, show an alert/notification/arrowbox offering to disable the version compatibility check for that add-on, enabling immediately the add-on for immediate use ; it should be a real warning box, of course...
  • if an add-on with compatibility check disabled is suddenly updated or auto-updated to a version matching Firefox, re-enable compatibility checking
  • modify the add-ons manager to make the above clearer and make it easier to enabled/disable the compatibility checking for a given add-on (there is currently no UI for that and that's really lacking)
  • when auto-update of add-ons is performed, let the user know if he/she has add-ons that are enabled only because their compatibility check is disabled

This is not an optimal solution, it's a short-term compromise to stop making users angry, in particular in the case of an add-on not served by AMO (and there are plenty of them) that could easily survive a maxVersion bump. Opinions?

Tuesday 12 July 2011

I still don't understand

I could have titled this article "I understand even less". Asa wrote the following in a comment on an article on Gerv's blog:

We have and we will break add-on API compatibility with every release, certainly binary add-on compat

I spent part of the night thinking about it but still, "Urgh..." is the only thing that comes immediately to my mind. I'm shocked, so shocked, you could not believe how shocked I am. Bumping version numbers every six weeks for strictly declarative (xul/js/css/xbl) add-ons is one thing and breaking binary compatibility for binary-based add-ons is another one. The former case is painful but doable in a lot of cases. I still think that add-on authors (I am an add-on author) will rapidly feel the pain but that's nothing in comparison with breaking binary compatibility every six weeks...

Some years ago, I contracted for Wengo, the VoIP division of a major telecom player here in France. We took their huge pile of binary libs, encapsulated them into binary components (painful but still simpler than js-ctypes) and I built both a SIP-based VoIP add-on for Firefox and a standalone application on that basis. Quite impressive, I must say. With a mandatory recurrent six weeks XPCOM component update/rebuild/reship process, my client would never have done that work because that's impossible to sustain.

On a more personal note, some of my personal add-ons to Firefox are binary-based, and there is no way I can dedicate time every six weeks to them. Most add-on authors work on add-ons on their personal time and will be in the same case.

Add-ons are the major plus Firefox and Thunderbird has over browser competitors. That ecosystem is unique. Harming that ecosystem is a counter-productive decision of such a magnitude I am completely lost these days reading Mozilla's strategic decisions. It seems to me the path taken is an engineer's path, not a market-based one. It seems to me based on a wrong analysis of the market, the competition, the users' needs and the marketable differentiating factors.

Our PR team and our Marketing team are happy with the current system and they're the ones on the front lines of "publicity". Also, that negative publicity has already happened. It's in the past. It may happen to a much lesser degree with 6 and probably even less with 7 and eventually it goes away as the version number disappearing act finishes

I think I see what's going on here. Asa is betting on the extinction of the criticisms over time. That's why despite of the incredibly negative press world-wide, we saw no serious reaction and why no improvement has been seriously discussed. The weekly meeting minutes of Moz are, from that perspective, incredible: almost no mention of the world-wide fuss Asa generated two weeks ago. First, that's certainly not how the community feels Mozilla should react. Gerv seems to agree (see comment starting with "That is one of the most depressing things I've seen you write in a long time"). This feels like an occasion long ago when Blake Ross was forced to "discuss in Bugzilla" something he had made a decision on, and responded by posting there one single word: "discuss."

At this point, and I never thought I could say that one day, I don't trust any more Mozilla's strategy for Firefox. I don't trust any more its Product Manager for Desktop Firefox. It's not the person, it's the strategy. I'm not angry, I'm incredibly sad. During all these years, I tried to draw the attention on markets addressable by Moz and not addressable by other browsers. I failed. During all these years, I did all my best to give my opinion about how to extend the ecosystem, the true cornerstone of Firefox's success. I succeeded implementing these ideas for my own product, BlueGriffon, but I failed for Firefox. I'm sorry, I'm so sorry.

At this point, I think the CEO of Mozilla should talk, loud and clear, and talk about this more with both the community and the users. Enough with corporate blah-blah, and I could say corporate bullshit.

Wednesday 29 June 2011

E pluribus unum

When I wrote my article The faster release process of Firefox, I did not expect so many reactions outside of the inner mozillian circles. I did not expect that Mike Kaply, who was thinking in the same terms and himself pondering an article, would jump on the bandwagon. I did not expect Asa's incredibly rough answers to his posts. In fact, I got many private messages thanking me for my article. I need to say it again here: I never said the faster release process is entirely bad. But that's another discussion.

I read things that really hurt the community and I think some conclusions have to be drawn, and some changes probably have to be applied.

  1. Mozilla is a lot of things. It's a Foundation, a Corporation, a large Community, millions of users, followers and evangelists. It's also a Manifesto, Products, Projects, Add-ons, Translations. For most of us in the Community, and for various reasons, Mozilla is also a very large part of our lives. We say "Mozilla should..." or "Mozilla should not..." because we do care about Mozilla, and we're not all nerds with only coding or localization abilities. We come from various landscapes, and if the coding skills of the community are used, the other skills are mostly ignored. The private comments on my blog post I received are very clear: some people did not want to express or delayed an opinion similar to mine in public (on a blog for instance) because they feared the reaction of Mozilla. Someone told me that "as soon as you start criticizing in public such high-profile decisions, you're tagged as a troll". I also got messages from add-on developers (XUL add-on developers I should say) saying they're fed up with the add-on update process, are afraid to have to do it now 10 times per year, and stating the new SDK supposed to resolve the issue does not offer them enough power for their extensions anyway. Like it or not, this is an indicator of a flakier relationship between the mothership and the community that has to be dealt with. Community does not need more goodies, it needs better integration and probably better support. Important detail: bugzilla and newsgroups are merely communication, and certainly not integration; and blogs sometimes, given the logorrhea of planet.mozilla.org, are a weak communication channel too.

  2. Freedom has many meanings, as we all know it. In the US, freedom of speech is almost total. Well, unless you start saying things that hurt your corporate employer for instance. In that case, freedom of speech often triggers the employer's freedom to let the employee go... Between the collapse of Netscape/the second birth of Mozilla and now, Mozillians (I mean employees here) have rarely, extremely rarely crossed the line. My old friend Tristan Nitot for instance always takes extreme attention to what he posts on his blog or even says in public because the distinction between perso and pro is never obvious. This is not easy to live like that when you work in a Free/OpenSource domain and I am the first one hit by the issue. My blog is my open diary, and I'm used to publish here exactly what's on my mind. But there's a big difference between my little, so little person and the Director of Firefox though: my visibility is low, very low. I don't represent officially an application used by hundreds of millions of people around the whole world and the whole world tech press is not all ears/eyes when I say or write something. Should the Director of Firefox be able to say in public, in the name of his personal freedom of speech, he/she finds brother product Thunderbird's UI offending and ugly and he/she stopped using it? Yes, he/she should be able to do it. But he/she should also be able to never forget again contributors are free to stop contributing. A balance of powers, clearly.

  3. Of course, given his visibility, his new position and the tone of his words, the whole world tech press has repeated ad nauseum Asa's words. Even if I think there's a serious strategic hole at the root of the problem, miscommunication did not help, to say the least. And miscommunication was created by misunderstanding and manichaeism. Nobody ever said Mozilla has to address all corporate needs, or has to provide ridiculous requests (Shaver said on his blog "one tab only", it's an excellent example) with a solution. As I said somewhere else, there is a large range of possibilities between "make corporations' lives easier" and "make corporations' lives harder". Given the world-wide reaction, I think it is now clear that the faster release process with fast EOLs causes the latter. Shaver and Sullivan said conversations with enterprises are ongoing. Better late than never. Don't forget governments, governmental or international orgs and military, please.

  4. The Community does not make any kind of difference between corporate and individual users. Their involvement in Mozilla is for all users, wherever they are, at work or not, in all countries, whatever the religion, race, colour, gender or opinions. It has to be understood that decisions that leave a given class of legitimate users on the side of the road - whatever the reason - are often seen as destructive by the Community. Hey, that's the weak side of OSS: you benefit from the good bits and have to live with the bad bits.

  5. The whole story reminds me of the "Get rid of the JS Console" frenzy a few years ago. The Community reacted loud and clear to that, and that decision was overturned. Now, a few years later, Firefox nightlies offers more and more developer tools and even more are coming. Firebug and the Developer panels of Chrome have shown that early adopters need web development environments that are not add-ons to the browser, maintained outside of the main stream, but built inside the main stream. Firebug is not distributed with Firefox probably because it induces footprint/performance hits but otherwise, it should be in. Please note this is why xulrunner-based app developers cry so much about Venkman: Chromebug has many issues in that environment and Venkman is most of the time broken, not really supported, and its feature set and severe bugs' list have not changed in years. Anyway, I wanted to mention the "Get rid of the JS Console" history because it seems to me (and it could be related to item 1 above and how the Community feels) that MoCo is more and more reacting as a microcosm. My discussions with the rest of community show an increasing number of "they're not listening, they say they are Mozilla and know" signals. MoCo, please, even if reading this you think this is a wrong reaction from the community, this is now far more than a few "trolls", it is factual and something must be done.

  6. There is a major difference of perception between Users/Community and MoCo about what is Mozilla and what should be its strategy. This is absolutely normal. MoCo has to deal with daily operations of a large and visible organization having a lot (yes, a lot, even if it's small compared to other big names of the industry) of employees distributed all around the planet. It has to secure revenue streams and make strategic choices. Even sometimes painful strategic choices. It's fighting for survival in a highly competitive landscape. Users and Community see Mozilla only as the browsing alternative, the freedom of browsing choice, the ability to get rid of IE handcuffs in corporate environments, and the cool kid around the block allowing a well-customized browser on all platforms. For them, Mozilla is the expression of its Manifesto, period.

  7. That feeling does not touch only the users or the Community. It apparently touches MoCo too. Reading #developers' monday IRC logs, the first word that came to my mind was "mutiny"...

  8. Users are versatile. Show them something cool and they'll adopt it. Both at work and at home. IE10 will be cool. Fast and reliable. Given the specs Microsoft is pushing inside the CSS Working Group (grid layout, templates, flexing, etc.), it is clear that standards-based apps and add-ons are in sight. Fear the revenge of the blue e... Those who think corporations will never have any incentive to go back to IE if they left it are in my opinion plain wrong. Those who think the only competitors to Firefox are now WebKit-based browsers are also plain wrong.

It's an old couple needing just a bit of couple therapy. Nothing more but nothing less. They still love each other, no worries.

Now, back to code.

Tuesday 28 June 2011

Instantbird 1.0 !!!!

The bird has left the nest : INSTANTBIRD 1.0, the Instant Messenging app based on Gecko/Xulrunner, IS NOW AVAILABLE !!! Mucho congrats guys !!!

- page 3 of 37 -