> It's great they did this, but the Google that is today cannot be trusted with data of public value anymore.

They never should have been trusted in the first place.

I agree!

(Though you cannot call just any method asynchronously; the interface's IDL needs specific annotations and the underlying object needs to implement ICallFactory.)

Just add async_uuid to your IDL locally and rerun MIDL. The server doesn't know or care that it's being called asynchronously. It's a pure client thing. If you're calling an IFoo in a different apartment, you can do the call asynchronously by changing your client configuration without the IFoo implementation having to be aware that anything is going on.

You can also use IRpcChannelBuffer3 to make the call asynchronously no matter what the IDL says. You'll have to write the proxy plumbing yourself, but it'll work, and you don't even need to rerun MIDL.

Cancer is not the only complication...

Exactly. Hypertension, emphysema, people who don't smoke not wanting to be anywhere near you,

There are projects such as Halide[1] that actually allow you to achieve performance without needing to resort to asm.

[1] https://halide-lang.org/

They've been available natively on Nightly with some basic UI support since they were first implemented a decade ago. Some other pre-release builds have them too but it's been too long and I cannot remember which ones did or didn't.

I don't use Nightly and I've been using containers for I think that long without any extension for it.

Edit: looks like I enabled them manually and couldn't remember/find it, it's in about:config under the name "privacy.userContext" instead of "containers".

as far as i remember, the low level container functionality was always in the core browser. what the extension adds is the UI to manage containers. with this change it appears the UI is merged back into the core browser.

It's been there just as long, turn it on with "privacy.userContext.ui.enabled" and manage them at "about:preferences#containers"

The addons added extra functionality but everything they've listed in this announcement is already there. Sounds like they're just flipping these two flags by default.

Ah, that explains why there is still NPAPI plugin support.

Yup. The only browsers that still support Flash.

*natively. You can run flash through ruffle in any of the modern browsers.

The modern native frontend APIs aren’t exactly lightweight themselves…

Yak shaving is only fun when you don't have managers who don't care about the circumstances breathing down your neck.

That is true for software engineering in general. If you have a manager like that nothing is fun. And the products you build are likely to be bad.

Better yet, find a manager like my own manager who spent a literal quarter yak shaving!

> Plus privacy.resistfingerprinting isn't enabled even when selecting "Strict" "Enhanced Privacy Protection" in the settings, great job there Mozilla.

That pref is there for the Tor Browser.

It's enabled by default in Tor Browser and I'm not sure it can even be disabled?

Also enabled by default for Konform Browser and Mullvad Browser, which borrow many of the privacy- and security-related patches from Tor Browser.

The SpiderMonkey team always had t-shirts made up of these.