@ljrk I certainly agree that moving to Swift would further isolate the development of WebKit.
And, yes, if there are still Objective-C components in the Safari UI, those could certainly be rewritten in Swift.
But the existing codebase of WebKit is already using a tight subset of C++. And it has strict memory management and error handling systems. My old gang has been working on this now for over 20 years and they kinda have it tuned by now. π