npub172v3nlrtzd8wssn8f3ckm47jtsxdhq0jakqua3crgrvn7mmv32vsju689n (npub172v…689n) Personally I wouldn't see myself using this new type. I mean, we already have named tuples and dataclasses which serve a similar role, and I already find the existence of those two types to be a source of uncomfortable ambiguity - not that they're the same, of course, but I often encounter situations where I could use either one and I have no good reason to choose one over the other, and the existence of record types as a third option usable in many of the same cases would only increase that ambiguity.
I suppose if other people find it useful, who am I to object - it's not really hurting me to have another type syntax that I never use - but I guess I just don't get it 🤷
#Python
David Zaslavsky /
npub105…0tsfs
2023-12-27 20:11:02
in reply to nevent1q…g7kw
Author Public Key
npub105vywj5u9qx5fkvuua6cq6xhmm2qmnltetnl0pqzk3wjn452fphsw0tsfsPublished at
2023-12-27 20:11:02Event JSON
{
"id": "0a96c0ac9b7bd40e4a8c15b9f0a1e5809bdc41a3820772b0ab14996d5e4f7849",
"pubkey": "7d18474a9c280d44d99ce7758068d7ded40dcfebcae7f78402b45d29d68a486f",
"created_at": 1703707862,
"kind": 1,
"tags": [
[
"p",
"f29919fc6b134ee842674c716dd7d25c0cdb81f2ed81cec70340d93f6f6c8a99",
"wss://relay.mostr.pub"
],
[
"p",
"4b4002d3714d074cc31210e9e65088406e9f62154010da12c339d41b18b30f21",
"wss://relay.mostr.pub"
],
[
"e",
"7d11e1996f236d11e113035edbb8cae623a3c2c8325a0887d3c571b6a394ea67",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"python"
],
[
"proxy",
"https://techhub.social/users/diazona/statuses/111654198451445354",
"activitypub"
]
],
"content": "nostr:npub172v3nlrtzd8wssn8f3ckm47jtsxdhq0jakqua3crgrvn7mmv32vsju689n Personally I wouldn't see myself using this new type. I mean, we already have named tuples and dataclasses which serve a similar role, and I already find the existence of those two types to be a source of uncomfortable ambiguity - not that they're the same, of course, but I often encounter situations where I could use either one and I have no good reason to choose one over the other, and the existence of record types as a third option usable in many of the same cases would only increase that ambiguity.\n\nI suppose if other people find it useful, who am I to object - it's not really hurting me to have another type syntax that I never use - but I guess I just don't get it 🤷\n\n#Python",
"sig": "f22533e2f7ded3dc21b9a735c991aebe6d940eb4bf346c8ad86a3449437a6ecd16158c7180d3fc939ca700dbba87eb5b7bc0a1ec6fdb96fc9a6f747bd5970b55"
}