Newest at the top
| 2025-03-25 06:21:25 +0100 | kh0d | (~kh0d@212.200.247.164) kh0d |
| 2025-03-25 06:21:04 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 244 seconds) |
| 2025-03-25 06:16:51 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) |
| 2025-03-25 06:16:51 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-25 06:16:32 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) (Ping timeout: 272 seconds) |
| 2025-03-25 06:14:08 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds) |
| 2025-03-25 06:09:16 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-25 06:05:12 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) |
| 2025-03-25 06:04:16 +0100 | cross | (~cross@spitfire.i.gajendra.net) (Quit: Lost terminal) |
| 2025-03-25 06:03:48 +0100 | kh0d | (~kh0d@212.200.247.164) (Ping timeout: 244 seconds) |
| 2025-03-25 06:03:46 +0100 | inca | (~inca@4-138-135-64.gray-ng.dsl.pinetreenetworks.com) (Ping timeout: 248 seconds) |
| 2025-03-25 06:00:58 +0100 | michalz | (~michalz@185.246.207.197) |
| 2025-03-25 05:58:54 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 260 seconds) |
| 2025-03-25 05:57:46 +0100 | <haskellbridge> | <dmjio> Parsing shouldn’t be any different. Servant handlers operate on an already parsed request, much like Scotty |
| 2025-03-25 05:57:34 +0100 | kh0d | (~kh0d@212.200.247.164) kh0d |
| 2025-03-25 05:53:29 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-25 05:53:08 +0100 | <haskellbridge> | <dmjio> The biggest upfront cost is the first request. The graph reduces and subsequent requests do less work |
| 2025-03-25 05:52:38 +0100 | jmcantrell | (~weechat@user/jmcantrell) (Quit: WeeChat 4.5.2) |
| 2025-03-25 05:51:02 +0100 | <davean> | dmjio that is also a lot of parsing via a lot of type level implied machinery |
| 2025-03-25 05:46:42 +0100 | aforemny | (~aforemny@2001:9e8:6cc3:cb00:4bbe:2838:488d:a24d) (Ping timeout: 276 seconds) |
| 2025-03-25 05:45:48 +0100 | weary-traveler | (~user@user/user363627) user363627 |
| 2025-03-25 05:44:56 +0100 | aforemny_ | (~aforemny@2001:9e8:6cde:a00:bd3b:75a2:c3bc:65be) aforemny |
| 2025-03-25 05:44:36 +0100 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 265 seconds) |
| 2025-03-25 05:42:40 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2025-03-25 05:37:43 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-25 05:36:38 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 272 seconds) |
| 2025-03-25 05:36:29 +0100 | <haskellbridge> | <dmjio> monochrom: That’s fair. |
| 2025-03-25 05:36:01 +0100 | <haskellbridge> | <dmjio> Liamzee: It wouldn’t surprise me at all if HasServer dictionaries weren’t getting specialized given the incremental compilation nature of GHC and cross module inlining limitations. But 5x still sounds heavy. |
| 2025-03-25 05:32:19 +0100 | notdabs | (~Owner@2600:1700:69cf:9000:c43:fe75:997:32d7) (Read error: Connection reset by peer) |
| 2025-03-25 05:31:47 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-25 05:28:34 +0100 | kh0d | (~kh0d@212.200.247.164) (Ping timeout: 260 seconds) |
| 2025-03-25 05:27:08 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 272 seconds) |
| 2025-03-25 05:25:18 +0100 | <haskellbridge> | <Liamzee> also re dmjio: it's possible servant breaks the specialization in warp, but i'm not really familiar with warp in terms of its type architecture |
| 2025-03-25 05:20:54 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-25 05:14:07 +0100 | <monochrom> | But we don't even need that for the inverse correlation between most used and most correct, no? Social media has also shown us the inverse correlation between most believed and most correct. Like we need to rationalize that. |
| 2025-03-25 05:12:25 +0100 | <monochrom> | Haskell or similar languages can be a sweet spot of not too many bugs and not too slow. |
| 2025-03-25 05:11:54 +0100 | <monochrom> | Oh Lean will never be as easy as C. Even Haskell will never be. |
| 2025-03-25 05:09:53 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2025-03-25 05:09:46 +0100 | <Axman6> | Looking at what the servers actually do, I would be surprised if there's heaps of overhead from using String, but there could be some. Changing it to Text should reduce conversions though |
| 2025-03-25 05:08:19 +0100 | <haskellbridge> | <dmjio> Zig embodies the Berkeley school philosophy which is why it will continue to succeed. |
| 2025-03-25 05:07:33 +0100 | <haskellbridge> | <dmjio> Axman6: Someone is sand baggin’ us |
| 2025-03-25 05:07:22 +0100 | <haskellbridge> | I am optimistic about Zig though. You have to keep the foot gun accesible. |
| 2025-03-25 05:07:20 +0100 | <haskellbridge> | <dmjio> Until you can make writing Lean as easy and as familiar as JavaScript, I don’t see the situation changing any time soon. |
| 2025-03-25 05:06:20 +0100 | <Axman6> | Well, when first looking at that benchmark, the Servant implementation uses String everywhere... |
| 2025-03-25 05:05:08 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-03-25 04:55:59 +0100 | <monochrom> | Sure. |
| 2025-03-25 04:55:55 +0100 | <haskellbridge> | <Liamzee> why does it have to be linear |
| 2025-03-25 04:55:48 +0100 | Square | (~Square@user/square) (Ping timeout: 245 seconds) |
| 2025-03-25 04:54:19 +0100 | <haskellbridge> | <dmjio> monochrom do you buy there is an inverse correlation between the most used software and the most correct software |
| 2025-03-25 04:54:03 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds) |