The thing that works in your favor is that Ladybird is very niche at this point, so unless some well-resourced adversary hates you specifically, it's unlikely that you'd be targeted.
The thing that works in your favor is that Ladybird is very niche at this point, so unless some well-resourced adversary hates you specifically, it's unlikely that you'd be targeted.
They do also benefit from using off-the-shelf libraries like Skia, OpenSSL, image libraries etc. that the other browsers are using too. Previously they were rolling their own for everything but changed after the split from SerenityOS.
It isn't as if Swift developer experience is that great outside Apple's ecosystem.
While I would definitly use it when on Apple's ground, I feel less inclined to thouch it for anything related to cross platform GUIs.
I haven't done a lot of Swift, but I did play around with it recently, and it seems to work fine even outside of the Apple ecosystem. It has a LSP you can use so you don't need XCode, they even develop a first-class plugin for VSCode.
That is indeed a serious problem for aspiring contributors to the project.
I keep hearing this - and have for years - but is it actually still true? Sure, you're never going to get Cocoa on non-Apple platforms, but with first-party VS Code support and a lot of the surrounding tooling open-sourced, is it all still [~that much worse than XCode~] as bad as all that?
Naturally most packages on the ecosystem assume libraries that don't exist outside Apple ecosystem.
Just like in the early .NET Core days, there were tons (and still are, hence businesses stuck in .NET Framework) that were actually wrappers to DLLs and COM based libraries.
Even Swift website acknowledges that the best use cases are command line and server stuff, the sweet spot is for server side applications for developers on Apple ecosystem, after all macOS servers are no longer something Apple sells.