Event JSON
{
"id": "131f0e8b3fe0f573b8c56164a7e31ff88c4ba2d00ef1755f747b5eb57736e698",
"pubkey": "2464a99bb3a2cface2d500032721fbdb4f036b4c92624d2039a11cc2d6a744a4",
"created_at": 1710511420,
"kind": 1,
"tags": [
[
"p",
"210f29ed96ca26d1fc8884365f15c97d659df551e62313d53c3cedfee0c9013b",
"wss://relay.mostr.pub"
],
[
"p",
"9a64dd44256e6741e56390a24c93311b2f8fe69dd81379b18b58fb9fec304a83",
"wss://relay.mostr.pub"
],
[
"e",
"8bd7f47520311df039ab89db022cf40f596d0de192514da858981efad54f5c71",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.alexn.org/users/alexelcu/statuses/112100076467671947",
"activitypub"
]
],
"content": "nostr:npub1yy8jnmvkegndrlygssm979wf04jema23uc3384fu8nklacxfqyas5vyfzq You may be right, but Future was also liked because the API was nice (e.g., flatMap, sequence), even if it was more error-prone. And the trouble with Java's thread-pools is that they are often limited, so blocking threads is error-prone. And Future did not have the performance of Cats-Effect IO.\n\nJava could've had one thread-pool, like System.Threading.ThreadPool from dotNET. Probably bad idea for constrained devices (Android), but not for server-side.",
"sig": "21c3d351f380073c1985e5b11135d6073566fd3bc5ca685f43f80d39009dd9abf128b23e286c61fbf411d06c84d7fcbe56b4f4e4068a2c14191da69d200f93b2"
}