Yup, though I wouldn't even say they "fixed it" with XAML islands since they lock you into .NET core 3...
They also keep doing boneheaded decisions like the new DWriteCore, which is a reimplementation of DirectWrite, and some features are only available in DWriteCore, but DWriteCore is not a strict superset and doesn't even interoperate directly with Direct2D like DirectWrite did.
So once again, either stay on the "stable" as people like to call it version, which is effectively frozen, or use the new one and rewrite half you app!
And then people wonder why nobody uses Microsoft APIs if they can avoid it.
They also keep doing boneheaded decisions like the new DWriteCore, which is a reimplementation of DirectWrite, and some features are only available in DWriteCore, but DWriteCore is not a strict superset and doesn't even interoperate directly with Direct2D like DirectWrite did.
So once again, either stay on the "stable" as people like to call it version, which is effectively frozen, or use the new one and rewrite half you app!
And then people wonder why nobody uses Microsoft APIs if they can avoid it.