Event JSON
{
"id": "ba3d5c7b276c796a50379e76d027d027882af950ef0ed87942149e7c6623d204",
"pubkey": "05bbadaea41d30c3cf3b7fb1027622eb00cca66635fc9047053df7f9a54cb0c7",
"created_at": 1702115007,
"kind": 1,
"tags": [
[
"p",
"d0be7f23cd807eb4607f11fa002f17286df210ab3825549308b2a584295a35bd",
"wss://relay.mostr.pub"
],
[
"p",
"e405dd9609a0e2dcac32ff4292654120a1df80a6554f6d376b809fb1e97b5845",
"wss://relay.mostr.pub"
],
[
"e",
"cdad56ac2c0840c207db10f0455c8a229abf4a9f4c378d8c8b1159bf3a751655",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/drewdevault/statuses/111549809126506462",
"activitypub"
]
],
"content": "nostr:npub16zl87g7dspltgcrlz8aqqtch9pklyy9t8qj4fycgk2jcg226xk7sd8y34r well, the language itself maintains great backwards compatibility, but the tooling and standard library does not tend to. I feel some Python-related trauma triggering when I see problems caused by Go modules -- Go modules are honestly great for the most part but they do cause problems where if I want to continue being invested in Go I need to continuously learn new tooling and work around new problems, and my existing code bitrots due to external forces.",
"sig": "ee83c0d9431899547df0357a53add355386097da4184c68f48bc25280420991be7855cca4274f19ebba7b7cddb2807d81f3830f71b6026bf016249355d879a83"
}
