>we'll rewrite it in Sw-ACK
>>108184976Swift somehow manages to be worse than Objective C, which was already a complete abomination. Apple can't into programming language design.
>>108184976https://github.com/LadybirdBrowser/ladybird/issues/933
How aboat Carbon?
>>108184976It was a bizarre decision to go for Swift but didn't expect them to go back on it so soon. I wonder if this pushes back their eta even further or what's happening
>>108184976>The Apple check bounced
>>108186912Apple runs on Java, why would they downgrade?
Meme web browser with a tranny name
>>108186881so it's mostly c++ interop issues.ironic that this greenfield browser is back to using an archaic language while the brownfield browsers are adopting modern languages.
>>108184976Good. Choosing Swift was the dumbest choice they made by far. Would like to have seen Zig or Go.
>>108186912Swift embedded is slowly becoming Rust.
>>108186896>literal coal lang
>>108184976I was going to say "Anyone with a brain could have told them that a browser in Swift is a retarded idea". But looks like it's mostly problems with the C++ interop, so I'll have to fall back to "Anyone with a brain could have told them that using two languages at the same time in such a big project is a retarded idea"
>>108186910I imagine the swiftness (no pun) is going to benefit the timeline, no? Better sooner than in the middle after already writing a ton of new code just to throw it out.>>108187245I've always considered checking it out but never had a reason to being a non-Mac user.By the time I would have had the skills to understand the language, I think I was already using other things.Still curious if it's viable as a language to start a new project in today, especially a non-Macos one.
What’s all this hate for swift? I haven’t used the language since its first inception writing iOS native applications. It was enjoyable. The worst part was dealing with Xcode. But the language itself was great to use. I miss it, now writing Kotlin garbage
>>108186857Honestly, I'm surprised Apple hasn't given up and just moved to Rust. that's basically what they've been trying to make Swift more like with every release. It just seems like Apple is incredibly incompetent, evil or both.
>>108189289clownshow language that gets bent over backwards to serve the interests of SwiftUI (a nightmare of bad) and other Apple shitware.
>>108187194>Goslow>ZigEven less memory safe than C++
>>108189289The main issue I have with it is the bad documentation (an Apple staple) and communication from the language developers in general. Other than that, it's a pretty good language. Fast, memory safe, good interop with Objective-C, lots of features and still easy to read and write.
>>108189289I've only used for toy things like AoC problems, but I thought it was pretty comfy to use. Maybe it gets unwieldy in large projects, or maybe /g/ just hates everything.
>>108189427Apple doesn’t have that bad of documentation. You need to learn how to search for it.> “{thing} Developer Guide”Or one other term I can’t remember now (was doing this in 2016). But these two search terms found me everything I needed to know about low-level swift and framework things. And their docs were great. Just hard to find.
>>108192303I think the other term was “Developer Reference” or something like that. Either way, using that included with what you are looking for almost always got me to where I needed
>>108184976What happened?>>108186857Swift is a beautiful language. It's a total joy to work in. Is it too high level for you autismos?
Swift is a great language, the decisions Apple made to enable SwiftUI in a rush were not.Result builders are full of footguns. And structured concurrency was dumb and rushed too, was made to appeal for JS retards and makes things 100x harder to write.
>>108189413yeah
>>108192728It's too high level.
