Aujourd’­hui c’est Google Chrome qui a la main et on voit appa­raitre le même schéma que par le passé. [...]
La situa­tion n’est pas exac­te­ment la même que celle des années 2000 mais elle n’est pas si éloi­gnées que ça.

Il y a plein de navi­ga­teurs mais en réalité Brave, Opera, Vivaldi, Inter­net Explo­rer et les autres sont des déri­vés de Chro­mium. Chro­mium c’est la base open source de Chrome, contrô­lée par Google.

Une fois qu’on a retiré tout ce qui se base sur Chro­mium, il reste Safari et Fire­fox.

Why Firefox forks is not a solution.

1. No fork is doing large-scale engineering work on the browser.
2. Some forks keep insecure APIs
3. Mozilla code is still running under the hood. They must be trusted as for the Firefox browser.
4. The fork is still 99.99% Mozilla code contributions
5. The fork can need more time to apply fixes

This platform shipped in Firefox 133 to provide alt text for images in PDF.js, and will be used in several other places in Firefox 134 and beyond to improve the user experience.

Many Tasks are available in the browsers, exposed in browser.trial.ml.

A simple comparison: Firefox uses less RAM.

Yes I feel it too. Other websites are fast, but somehow it is slow on youtube.

A incredible performance optimisation for WebAssembly in Firefox!

(via https://korben.info/firefox-accelere-execution-webassembly-75-fois.html)

For example, the compilation time of the WebAssembly module used by Adobe Photoshop online was reduced from 4 minutes to just 14 seconds. Similarly, a test module for the JetStream 2 benchmark saw its compilation time reduced from 2.8 seconds to 0.2 seconds.

Tips du jour: dans Firefox, il y a le raccourci clavier «'» (quote simple, touche 4 du clavier). Ça ouvre un menu de recherche rapide de lien dans la page. On tape du texte, ça cherche les liens qui contiennent ce libellé, et il suffit de valider pour suivre le lien. Ça permet une navigation rapide sans quitter le clavier des mains !

Ok ok

The UI is not directly tested but each element has a unique ID.
We can then check the state of each element to ensure they are correct.

During the Pwn2Own competition. From the outside, this competition seems crazy: so much vulnerabilities are found.

So it seems that the word's out, there will be layoffs at Mozilla. What is maddening about this is that the company is in a very good spot financially speaking. Just check the last public audited financial statement: assets.mozilla.net/annualrepor

Expenses have been significantly lower than income and the company has significant assets that could cover Firefox development expenses for years.

Also Mozilla Corporation has no investors to cater to, it doesn't pay dividends to anybody, nobody gets a bonus for this. It makes absolutely no sense.

The big issue here is, Desktop browsers are irrelevant. Same for people that may read this is on Mastodon.

The vast majority of browser activity is coming from young people (12-25), which use their mobile device for browsing. And, believe it or not, these folks click way more content in a minute than I do.

Still, it would be nice to have 100% FF users on my blog, at least if they are using Linux. But even there it is 50/50.

More and more of the traffic comes from mobiles and the young are the majority of this browsing activity. It is different for companies though!

These bugs highlight the risk of unknown unknowns, i.e. stability issues in our stability monitoring itself that we are blind to