2025/04/16

Newest at the top

2025-04-16 13:15:00 +0200haritz(~hrtz@user/haritz) haritz
2025-04-16 13:15:00 +0200haritz(~hrtz@152.37.68.178) (Changing host)
2025-04-16 13:15:00 +0200haritz(~hrtz@152.37.68.178)
2025-04-16 13:14:12 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-16 13:13:46 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 265 seconds)
2025-04-16 13:11:20 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds)
2025-04-16 13:07:58 +0200jacopovalanzano(~jacopoval@cpc151911-cove17-2-0-cust105.3-1.cable.virginm.net) (Client Quit)
2025-04-16 13:06:46 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-16 13:04:45 +0200jacopovalanzano(~jacopoval@cpc151911-cove17-2-0-cust105.3-1.cable.virginm.net)
2025-04-16 13:00:10 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) lortabac
2025-04-16 12:53:28 +0200xff0x(~xff0x@2405:6580:b080:900:121f:92ea:5a7d:afb)
2025-04-16 12:52:33 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-04-16 12:45:46 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-16 12:43:10 +0200__monty__(~toonn@user/toonn) (Ping timeout: 276 seconds)
2025-04-16 12:40:41 +0200pavonia(~user@user/siracusa) (Quit: Bye!)
2025-04-16 12:39:07 +0200Digit(~user@user/digit) Digit
2025-04-16 12:35:47 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-04-16 12:35:22 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 276 seconds)
2025-04-16 12:32:31 +0200gmg(~user@user/gehmehgeh) gehmehgeh
2025-04-16 12:32:00 +0200gmg(~user@user/gehmehgeh) (Ping timeout: 264 seconds)
2025-04-16 12:30:39 +0200Digit(~user@user/digit) (Remote host closed the connection)
2025-04-16 12:30:12 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-16 12:25:18 +0200euleritian(~euleritia@dynamic-176-002-178-231.176.2.pool.telefonica.de)
2025-04-16 12:24:34 +0200 <[exa]> (other than that it's probably quite easy to do the server&client layer with a bit of haskell. streaming libraries can help you with parsing the command stream)
2025-04-16 12:24:21 +0200euleritian(~euleritia@ip5f5ad695.dynamic.kabel-deutschland.de) (Ping timeout: 252 seconds)
2025-04-16 12:23:39 +0200 <[exa]> Morj: how much other programs do you need to talk to it?
2025-04-16 12:18:19 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-04-16 12:17:04 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 245 seconds)
2025-04-16 12:13:12 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-16 12:07:45 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-04-16 12:06:55 +0200turlando(~turlando@user/turlando) turlando
2025-04-16 12:04:17 +0200euleritian(~euleritia@ip5f5ad695.dynamic.kabel-deutschland.de)
2025-04-16 12:03:27 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-04-16 12:03:02 +0200euleritian(~euleritia@176.2.178.231) (Read error: Connection reset by peer)
2025-04-16 12:02:50 +0200j1n37(~j1n37@user/j1n37) j1n37
2025-04-16 12:02:43 +0200lxsameer(~lxsameer@Serene/lxsameer) lxsameer
2025-04-16 12:01:44 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 260 seconds)
2025-04-16 11:59:51 +0200L29Ah(~L29Ah@wikipedia/L29Ah) L29Ah
2025-04-16 11:59:22 +0200euleritian(~euleritia@176.2.178.231)
2025-04-16 11:59:03 +0200euleritian(~euleritia@ip5f5ad695.dynamic.kabel-deutschland.de) (Ping timeout: 268 seconds)
2025-04-16 11:57:45 +0200Unicorn_Princess(~Unicorn_P@user/Unicorn-Princess/x-3540542) Unicorn_Princess
2025-04-16 11:57:26 +0200 <haskellbridge> <Morj> I'm actually looking for a replacement for our grpc which supports backwards connections: it's a server that establishes the connection to the client, and then the client sends requests
2025-04-16 11:56:39 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Ping timeout: 245 seconds)
2025-04-16 11:56:19 +0200 <haskellbridge> <Morj> Indeed, why do I
2025-04-16 11:56:14 +0200xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 245 seconds)
2025-04-16 11:54:28 +0200 <[exa]> Morj: yeah but it's lovable no? why do you need RPC in 2025?
2025-04-16 11:53:34 +0200 <[exa]> bwe: as the initial hint you get the information that stateful functions can be represented as (s -> (result, s)), possibly with more parameters such as (a->b->s->(result, s)), then you add Functor Applicative Monad instances and eventually it just works
2025-04-16 11:52:40 +0200 <haskellbridge> <Morj> That sounds more like an idea than a concrete rpc with a library and shit :]
2025-04-16 11:52:36 +0200 <[exa]> bwe: tbh I'd recommend just biting the bullet and trying to reimplement the thing yourself, it's most effective
2025-04-16 11:51:52 +0200 <[exa]> remote lambda application