Thread

1. someonebaggy · 1790596609 · focus · HN ↗

   Vibecoded?

   1. bigfishrunning · 1790599313 · focus · HN ↗

      clearly.

      1. nateb2022 · 1790626909 · focus · HN ↗

         As someone very critical of mindlessly vibecoded software, I've worked with James (@prologic) years ago and very much respect his craft. AI assisted or not, I wouldn't describe him as a vibecoder. He's a great engineer.

         1. dgl · 1790642354 · focus · HN ↗

            As someone who has worked on IRC protocols, I wanted to understand how this actually works, but the docs are so LLM generated this is not worth my time:

               Everything that carries what somebody said is written down as owed to each instance it is owed to, and delivered from there: a direct message, which has nowhere else to come from, and a channel message, which used to be offered once and forgotten.
            
               The forgetting was not obvious, because it usually did not show. An instance that had gone away noticed on the way back and walked the feed in section 7, and the message arrived late rather than never.
            

            That&#x27;s not how you document a protocol. From <a href="https:&#x2F;&#x2F;git.mills.io&#x2F;prologic&#x2F;parley&#x2F;src&#x2F;branch&#x2F;main&#x2F;docs&#x2F;PROTOCOL.md#deliveryhttps:&#x2F;&#x2F;git.mills.io&#x2F;prologic&#x2F;parley&#x2F;src&#x2F;branch&#x2F;main&#x2F;docs&#x2F;PROTOCOL.md#delivery" rel="nofollow">https:&#x2F;&#x2F;git.mills.io&#x2F;prologic&#x2F;parley&#x2F;src&#x2F;branch&#x2F;main&#x2F;docs&#x2F;PR...

Unofficial Hacker News client; not affiliated with Y Combinator.