3 ms·
The worst part is not only that the documentation is awful but that Apple uses needlessly overcomplicated OOP design on top. It’s just a bad experience all arou
by bowsamic 3y ago
The worst part is not only that the documentation is awful but that Apple uses needlessly overcomplicated OOP design on top. It’s just a bad experience all around. I don’t think SwiftUI is any better either, though it avoids the old OOP mess it is still very complicated and if you want to do anything not immediately supplied by the library you often are best falling back to AppKit anyway. It’s just very unpleasant programming in general
- kalleboo 3y agoSwiftUI started out really simple but now that they're extending it to cover more functionality it's getting more and more complicated. Instead of complicated OOP design now it's inscrutable functional design, now with the bonus of Swift's "less verbose" syntax and naming. I was dealing with TransferRepresentation the other day and this API must be extremely confusing to someone who's new to Swift. The documentation reads like you're supposed to already be familiar with some concept that is never explained.
- bowsamic 3y agoI totally agree. The code supporting the “concise” framework is so complicated it’s almost impossible to add any functionality