I read the entire thing and still can't tell if this is a joke.

Reminds me of http://www.realultimatepower.net/

Oh, that's good. "Facts: 1. Ninjas are mammals."

Author note: Hopefully you have fun with this. You can compare the performance of your phone to your workstation on any architecture. I'm having fun learning about WASM performance and loving that Firefox is somehow the BEST WASM engine in the game right now. Super fun!

I use MDN heavily every day and this is really depressing. When I first landed on a fresh page today I thought I'd clicked on the wrong link and got some low-rent MDN knockoff by accident. It instantly looked cheap and jarring on a squint test.

Also, why is everything error-toned? Red is a danger color and invokes negative emotion almost universally. Red MDN!? Really?

I'm a browser extension developer and I'm strongly considering burning a week to write an extension to fix this.

> Also, why is everything error-toned? Red is a danger color and invokes negative emotion almost universally. Red MDN!? Really?

It's not all red. They've color-coded each page by whether it's about HTML (red), CSS (blue), Javascript (orange), HTTP (green), or Web APIs (purple). The Web Technology section is also blue for some reason.

Why would they do that, what's the point beyond confusion? The whole thing is bad

Oh, thats why the colors change. It actually hurts my eyes when jumping from link to link. So far, the purple is the worst (makes it hard to read).

Could not agree more! Firefox begining to support V3 is also extremely troubling; regardless of the compromises they are offering for adblockers. We need to resist this.

V3 is a cancer. As a full time extension developer I am dreading the notion of chrome successfully deprecating V2. Hopefully developers can rise up against V3 before it's too late.

What changes are you most concerned about? How does Manifest V3 negatively impact your extensions?

You may want to consider getting involved in the recently announced WebExtensions Community Group in order to discuss your concerns with the future of browser extensions with browser vendors and other extension developers.

http://w3c.org/community/webextensions https://github.com/w3c/webextensions

What action can we take? Switching browsers is hardly going to make G blink.

Edit: I want add, recently built my own Firefox - pulled out all the Pocket shit and tweaked the UI a bit "my way". Was actually not that hard. I'd love to see 20 forks of Firefox trying different things. Also, anyone know what happened to Librefox?

Get enough attention from the EU, to get them to determine that on balance, Manifest v3 is designed to cripple ad blockers and abuse Google's monopoly on web browsers to benefit their monopoly on search advertising.

Until Firefox us taken seriously by tech companies not google , it's inevitable. I've yet to encounter a website that doesn't work on chrome , but FF is a gamble between it not being supported or prevent ad tracking breaks it. Can't use teams in web despite it running a bit better than desktop , can't use most of my apple websites for work, least not without some extension so it's really just frustrating.

Honestly if chrome introduced bottom url bar and extensions without limitations... I'd switch back. I didn't switch for privacy but because chrome mobile is is clunky as a web app and I use my phone a lot during the day.

I can count the number of times a website has not worked for me in Firefox the past 5 years on one hand.

Now contrast that with the number of extensions Chrome would break for me with this update. It's a bigger number. Luckily I'm already on FF.

That seems doomed to eventual irrelevance since web standards are now constantly-moving goalposts also authored by companies like Google.

This is my place to plug once again that Slack still doesn't support calls on Firefox, over four years since they were launched.

Users moved to Chrome and Firefox in part because of extensions. If users start getting notifications that their favorite extensions are no longer available on Chrome and they'll need to move to something else.. they're likely to follow.

Do you have a blog post about your build procedure?

No. I started here https://davidwalsh.name/how-to-build-firefox - it mostly "just worked". I'm on Gentoo so I already had all the build-deps (oh, I had to enable some PulseAudio crap tho)

Netscape ran on Unix platforms.. buggy or not its support was vastly more important than IE on an ethical level.

I used NN3 and 4 back in the day (and still do, kinda, Firefox is still my main browser), but man, writing CSS for Netscape was a nightmare!

I still remember that weird bug that forced everyone to create a single, empty, invisible DIV at the beginning of the page if you wanted to set absolute positions for the other DIVs in the page.

In Javascript land, we all had our little script to detect the browser and do things like finding the element you wanted (IIRC, only IE had find by id).

All in all, I miss the carefulness webdevs had to have at the time (I remember uglifying my files by hand to make everything weight less than 24KB, which was the self-imposed limit we had at the dotcom I worked at) but, in general, I don't miss those days at all.

NN didn't actually do CSS, it did JSS (Javascript Style Sheets, something Netscape hoped would fly) with an added translation layer. That meant that you could only style an element through its hierarchy (since there was no equivalent of IE's document.all in Netscape's DOM). $DEITY help you if you were trying to do a hybrid tables/CSS thing, especially with nested tables.