GC vs Borrow checker is down to trade-offs. The former is a well proven strategy, probably easier to implement and less verification work for the compiler. For the time Go was released, it's understandable they went with GC.
Agree on the learning curve.
Would be interesting to see a third language, striving for simplicity and fast compilation but with borrow-checking.
Lumor /
npub1r0…z2qfw
2023-08-02 22:07:32
in reply to nevent1q…20wh
Author Public Key
npub1r03dske8jlrlkna4ry3uayj52e0prgy03m865qfj540vdzx9s7eq4z2qfwPublished at
2023-08-02 22:07:32Event JSON
{
"id": "8266a749aeebb29717d33a8cfcd6fda766ca8bf6eeaf8da7e19596a3e3dc9806",
"pubkey": "1be2d85b2797c7fb4fb51923ce9254565e11a08f8ecfaa0132a55ec688c587b2",
"created_at": 1691006852,
"kind": 1,
"tags": [
[
"e",
"e296a25755dbb765e6a167f91090a03312c462d1320e7c23691ea69800188cac",
"",
"root"
],
[
"e",
"55dffdfcad1f9c8154eab1b1b1b9aae088bfbd17b681cf20307dd026c452ebd7"
],
[
"e",
"9f2dc30a71b59c8dca6ed8e6c320b1882b937d0f396206406a0430626884dc8b",
"",
"reply"
],
[
"p",
"1be2d85b2797c7fb4fb51923ce9254565e11a08f8ecfaa0132a55ec688c587b2"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"3628e6a5764cacab310474c9f9c588657989c74b5ef0718c7e6e0e53a2a1f773"
]
],
"content": "GC vs Borrow checker is down to trade-offs. The former is a well proven strategy, probably easier to implement and less verification work for the compiler. For the time Go was released, it's understandable they went with GC.\n\nAgree on the learning curve.\n\nWould be interesting to see a third language, striving for simplicity and fast compilation but with borrow-checking.",
"sig": "de7c838b9e5b9faa1e8452c5be86f2a145078984e012e2e9e19b56fccdbf4bfd663daab2ca7dc98693f2beec02e9ff9ac9a5eb20d067b640c4befbe4c692900e"
}