if you knew about how there is HTTP version two, often writt...

原始 JSON

{
  "kind": 1,
  "id": "fe94b928cae328446e90b5204e08d3ed2f41a230b1135ac6bf775c3a1efcd875",
  "pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
  "created_at": 1776818939,
  "tags": [
    [
      "client",
      "https://smesh.lol"
    ]
  ],
  "content": "if you knew about how there is HTTP version two, often written http/2 - you may not have realised that this new standard, which almost nobody uses yet, still, requires libraries supporting it to have JSON codecs in it.\n\nwhat the fuck were W3C thinking about by binding javascript object notation into http? clear case of what the fuck dude. javascript is fucking javascript. not every fucking webserver uses javascript as the language. javascript is an utter shit language for writing servers. it was originally designed for scripting web pages. putting it in a HTTP standard is so arse backwards i just can't even.\n\nmoxie doesn't have json in the stdlib currently because the one it would inherit from golang is a piece of junk that breaks nostr encoding, and i wrote a fast json encoder for nostr anyway which is almost as fast as a TLV encoder, in the decode step.\n\nthe go stdlib is an absolute travesty.\n\nand in general, the whole reason i made moxie is because i got sick to death of so many stupid things in go, the work stealing scheduler, the stdlib and a dozen things inside it especially including the net libraries using reflection for no good reason. reflection altogether is unnecessary. a language that supports CSP should not be mashing that together with shared memory parallelism either. the overhead on doing parallel processing on Go because of that scheduler at least back in 2020, was 20% less than using multiple kernel processes connected by a socket IPC. which is why moxie has spawn() and why moxie doesn't have parallel processing within threads. CSP concurrency is essentially a simplified event driven programming dispatch mechanism. moxie has this instead. sending on channels does what you intuitively sense it should do - move processing to the select that contains the channel - and it should only be able to have one of those, because otherwise in the parallel threading what the fuck. really, that's why they called them goroutines instead of coroutines. they are a frankenstein of Hoare's CSP and some kind of retarded C++ style pthread shit.\n\nhmmm that's a thought. i currently have moxie doing the whole spawn thing through launching a process. there's no reason i can think of why it shouldn't be done as a normal pthread library thing.\n\nanyway. http/2 is bullshit. making everyone have to support json encoding, the most awful plaintext codec in the universe, is just not ok man.",
  "sig": "110878e3da550e5fa0e264d370c9bcca58cb937b165b8b734d2eede46105f87190fcf2bbca9437d7e5baf50d567e0a1bbdf665b43dc534473326a3cce2594cd4"
}