4 ms·
I think it's pretty simple - there's just so much more open source PHP code out there in the LLM's training dataset. Swift has been around for much less, and mo
by sleepy_keita 4mo ago
I think it's pretty simple - there's just so much more open source PHP code out there in the LLM's training dataset. Swift has been around for much less, and most Swift is closed-source - not that many years have passed since Swift has been able to run on non-Apple platforms, too.
- iamcalledrob 4mo agoI would also bet that 90% of Swift training data is UI code. And UI code quality tends to be technically pretty crummy/low-discipline. Your UI code doesn't need much consideration around data races, for example.
- ChrisMarshallNY 4mo agoYou wouldn't know that, if you looked at the UI code the LLM gives me. It loves threads; often mixing GCD and async/await, in one function. A lot of the code I need to tear out, looks like that. Most of the code I write is UI. It's actually fairly intense work, but relies on the underlying SDK, rather than language tricks. I find the UIKit code I get, is a lot more robust and performant, than the SwiftUI code.
- psychoslave 4mo agoPHP changed a lot since its early days. To the point where anything old would be considered bad practice by contemporary ecosystem point of view. So duration is not all. Comparatively, C seems to have stick to the same idiom all the way. That's not to praise C style form here to be clear, which is ridiculously obfuscating and feeling like pointless collection of linguistic awkward atrocities. But at least it's consistent in doing it.