David Beck :xcode: on Nostr: Overall, SwiftUI feels like its creators are terrified of backwards compatibility. ...
Overall, SwiftUI feels like its creators are terrified of backwards compatibility. Like if they exposed the internal structure of Font (which is more complicated than UI/NS/CFFont) that would lock them into that API contract.
And to be fair, there are no good solutions for this problem, and it is an industry wide problem. Whether it's a programming language or library, we don't have a good way to evolve without breaking or reinventing.
Published at
2024-04-23 19:48:31Event JSON
{
"id": "895b737fb02e4467841f589d128accaf3aceb44d26486de278865ab914cb1ca9",
"pubkey": "347e56e8185507e0543f70ae84bb97cf5f4f23ad4782daacd437ac53a1519634",
"created_at": 1713901711,
"kind": 1,
"tags": [
[
"e",
"62c716e59ffffab5e95a90bd8366305e2fc3453f8b1d4c5a6d1d1ec08c5cbc45",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://tnku.co/users/david/statuses/112322262579598268",
"activitypub"
]
],
"content": "Overall, SwiftUI feels like its creators are terrified of backwards compatibility. Like if they exposed the internal structure of Font (which is more complicated than UI/NS/CFFont) that would lock them into that API contract.\n\nAnd to be fair, there are no good solutions for this problem, and it is an industry wide problem. Whether it's a programming language or library, we don't have a good way to evolve without breaking or reinventing.",
"sig": "95f5c6d620957d7f293144e67f27d5630978589bbd0e15e888cab8868072fefe8fb9525f4b73614217a5f15496b9adcfafce2aef051ec5b552565db2c63a5c80"
}
