Experimental browser for the Atmosphere
Loading post...
{ "uri": "at://did:plc:l3rouwludahu3ui3bt66mfvj/app.bsky.feed.like/3lo6vwcqllm2y", "cid": "bafyreiavbmsp2apz6ntdrf4v2b25dowgsrjs6ozs4vwv3oozmf2xjncnfy", "value": { "$type": "app.bsky.feed.like", "subject": { "cid": "bafyreicr6dzyqzvq3v7jdxonhjvq3m7mgruc5ncbqd5skk6hc6s6zx2nqi", "uri": "at://did:plc:q6gjnaw2blty4crticxkmujt/app.bsky.feed.post/3lo6cluav4c24" }, "createdAt": "2025-05-02T13:17:23.460Z" } }
I'm trying to figure out why Go Channels feel weird in some use cases for high performance applications and I think I have a thesis: Channels are good for fan-in or fan-out but awkward when fanning in to fan out again. Multi-producer to multi-consumer patterns should share goroutines via callbacks
May 2, 2025, 7:31 AM