David Beck :xcode: on Nostr: I always find it interesting to compare SwiftUI to React because they both run into ...
I always find it interesting to compare SwiftUI to React because they both run into the same challenges but often solve them in very different ways.
Take for instance the problem of representing child components. SwiftUI pushed result builders through to be a core language feature. React basically invented a new superset language that transpiled back to js (
https://legacy.reactjs.org/docs/introducing-jsx.html).
Published at
2024-07-15 15:07:46Event JSON
{
"id": "1004fd083765a8c4ff2f2de6992e85ba2bc581216f76a74d614fe67c59729295",
"pubkey": "347e56e8185507e0543f70ae84bb97cf5f4f23ad4782daacd437ac53a1519634",
"created_at": 1721056066,
"kind": 1,
"tags": [
[
"e",
"157a44c207832037c1aff1a14dbcf7769be958cae9a482248402ecfbdbfc9a50",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://tnku.co/users/david/statuses/112791130352958860",
"activitypub"
]
],
"content": "I always find it interesting to compare SwiftUI to React because they both run into the same challenges but often solve them in very different ways.\n\nTake for instance the problem of representing child components. SwiftUI pushed result builders through to be a core language feature. React basically invented a new superset language that transpiled back to js (https://legacy.reactjs.org/docs/introducing-jsx.html).",
"sig": "3864360d0062146472756f47d7cee11e9643a8bf33f62891c91c03a47b37f6ca8f489d42b6f4db12a27d8c191465cdf0f95f397d30ce8ba59b57258c92328f3d"
}