This is, of course, the pettiest way that Apple could have possibly complied with the EUs orders while still insisting that only they know what's best for their users. Which is why it's completely unsurprising.
https://www.theverge.com/2024/1/25/24050478/apple-ios-17-4-browser-engines-eu
What's fascinating to me here is that Apple is being visibly angry with the decision instead of handwaving it as "Oh, we're doing this because we chose to, and the pending legislation has nothing to do with it" like they did with implementing RCS.
My gut says that it's because they view the web, untethered from their underfunded browser, as a real threat to their app store model.
Also, even with RCS enabled they can still argue (with good reason) that the Apple-owned experience is superior. They can't do that with their browser.
@tojiro And subscriptions outside the App Store! It's as if there's a pattern....
@tojiro How ironic, I tried to reply using Apple's browser, but I couldn't get it to show my keyboard...
@kainino0x rofl
I wonder what they consider to be "features that improve memory safety".
Chromium Rust re-write incoming? 
@tojiro @kainino0x Have you seen Chromium mitigations? See https://security.googleblog.com/2022/09/use-after-freedom-miracleptr.html. That should (hopefully) qualify.
@avidrissman @tojiro I hope so! Our project (Dawn) is getting actively MiraclePtr'd right now :)
@kainino0x @avidrissman @tojiro It's an interesting condition. They could perhaps always use whatever they do as a baseline to compare. And that could change quickly.
@kainino0x @tojiro Sorry, the phrasing in the discussion had me thinking non-Googler. Yep, welcome to the MiraclePtr world. Easier than a Rust rewrite, anyway.
Oops turns out I was reading the wrong part of the page. There's "Embedded Browser Engine Entitlement" and there's "Web Browser Engine Entitlement" and it's very easy to lose track of which one you're looking at because they have nearly identical content.
Here's an actually useful analysis of the terms:
https://open-web-advocacy.org/blog/owa-review-apple-dma-compliance-for-web/
@kainino0x Consider me absolutely shocked that you got confused reading through the volumes upon volumes of restrictions on the page.