They did not "artificially limit" the extensions available, you are misinformed.
They rewrote the engine of their mobile browser, and swapped the old engine for the new one before the new one had 100% support for all of the extension APIs. They have been working on this, and over the past few months I've seen several of my extensions which were previously disabled start re-enabling themselves as support for those APIs has been added. The eventual goal is to support all of the extensions that were supported before.
You can track that progress here: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...
It sucks that, for the span of a couple months, I lost a couple of my addons, but as someone whose team has struggled for years supporting two very different versions of a piece of software simultaneously, I understand why they did it. And the new browser is so much faster and more responsive that my annoyance about the addons was tempered somewhat.
>Now they're firing the Rust team? Are these people stupid? Rust is pretty much the only thing Mozilla has going for it. I guess it's time for Thunderbird to go as well.
They did not fire the Rust team. They laid off a few of the people who had been working primarily on Rust, and retained several others. But significant components of Firefox are written in Rust, and the people who are working on those components are still employed. And significant amounts of new code is being written in Rust - but essentially they can't swapping out hundreds of thousands of lines of code at a time anymore.
