> I haven't seen anything on memory vulnerability issues.
The issue is that barely nobody uses the Ladybird yet, so there are zero interests for anyone serious party to test that security. So nothing gets published about the issues. I don't even know if Ladybird runs in Google's Clusterfuzz.
Memory safety is their long term plan (according to them), and they are going to use Swift for that. Let's see what happens.
Has/will Swift be sufficiently disentangled from Apple influence?
And is this redirecting open source in an essentially proprietary direction (which has happened many times), on the key piece of software that is the Web browser?
Why I'm asking: For a startup, I've used Swift (and SwiftUI, various Apple APIs, "entitlements", developer-hostile App Store experience, often nonexistent documentation). The core language is OK overall (not great). But most of the rest of the developer experience was awful, due to Apple. And you need a lot of pieces beyond the core language.
Ultimately, the people who fund/do the work get to decide how they do it.
I personally wouldn't invest in increasing open source adoption of an Apple property like that, unless someone has a compelling new argument for that.
> I personally wouldn't invest in increasing open source adoption of an Apple property like that, unless someone has a compelling new argument for that.
> Over the last few months, I've asked a bunch of folks to pick some little part of our project and try rewriting it in the different languages we were evaluating. The feedback was very clear: everyone preferred Swift!
> First off, Swift has both memory & data race safety (as of v6). It's also a modern language with solid ergonomics.
> Something that matters to us a lot is OO. Web specs & browser internals tend to be highly object-oriented, and life is easier when you can model specs closely in your code. Swift has first-class OO support, in many ways even nicer than C++.
> The Swift team is also investing heavily in C++ interop, which means there's a real path to incremental adoption, not just gigantic rewrites.
The issue is that barely nobody uses the Ladybird yet, so there are zero interests for anyone serious party to test that security. So nothing gets published about the issues. I don't even know if Ladybird runs in Google's Clusterfuzz.
Memory safety is their long term plan (according to them), and they are going to use Swift for that. Let's see what happens.