5 ms·
They are planning to use swift in the future. Last point: https://ladybird.org/#faq https://ladybird.org/#faq
by mnmalst 1y ago
They are planning to use swift in the future. Last point: https://ladybird.org/#faq https://ladybird.org/#faq
- heavyset_go 1y agoI think that was being blocked by Swift features/libraries not being consistent across platforms, in that Swift for Linux/etc is missing stuff you'd get in macOS. I don't see that changing any time soon. If Apple truly wanted Swift adoption to be cross platform, they have the resources to do it, but they didn't do it.
- stephen_g 1y agoNo, pretty sure that's all basically fixed in Swift 6 (Sep 2024), I think it's more just the immaturity of the C++ interop in being able to bridge Swift to complex C++ code. That's a key feature of what Apple want Swift for (to gradually replace their C++ projects with Swift) but it's still pretty new. It'll take a while to mature.
- echelon 1y agoThat feels like the wrong language to bet the farm on. Swift is horrible to develop in cross-platform. The language ergonomics are great, but the support just isn't there. Also - swift is great for lots of applications, but a browser? Why use a garbage collected language for something that needs to be smooth? Unpredictable GC pause jitter is not something you want when smooth scrolling and rendering. Granted Javascript already negates that experience a little bit, but why introduce even more unpredictability? I get the feeling the leadership loves Mac/Apple, which makes sense in light of their recent iOS announcement. Maybe they're prioritizing that world.