2024/05/21

Newest at the top

2024-05-21 22:07:20 +0200 <lxsameer> monochrom: i'm looking for a way to let the user configure the app
2024-05-21 22:05:23 +0200 <monochrom> At which point it is 3 libraries, one for each input format. But then all 3 already exist.
2024-05-21 22:04:57 +0200 <monochrom> I would think I would prefer mapping all of cli args, yaml keys, env vars to my internal algebaric data type, not among themselves, why would I need that.
2024-05-21 22:03:39 +0200jcarpenter2(~lol@2603:3016:1e01:b980:f1ac:fe7d:6abe:6f13)
2024-05-21 22:01:31 +0200jmdaemon(~jmdaemon@user/jmdaemon)
2024-05-21 21:58:33 +0200 <lxsameer> is there any library to manage user configurations? for exmaple automatically map cli args to yaml keys and env vars?
2024-05-21 21:52:42 +0200basicnpc(~asleep@user/basicnpc) (Remote host closed the connection)
2024-05-21 21:52:42 +0200basicnpc(~asleep@user/basicnpc)
2024-05-21 21:49:49 +0200waleee(~waleee@h-176-10-144-38.NA.cust.bahnhof.se)
2024-05-21 21:47:48 +0200y04nn(~username@2a03:1b20:8:f011::e10d)
2024-05-21 21:47:40 +0200aryah(~aryah@141-138-38-218.dsl.iskon.hr)
2024-05-21 21:47:34 +0200y04nn(~username@2a03:1b20:8:f011::e10d) (Remote host closed the connection)
2024-05-21 21:47:00 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-21 21:47:00 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-21 21:41:42 +0200aryah(~aryah@141-138-38-218.dsl.iskon.hr) (Read error: Connection reset by peer)
2024-05-21 21:41:22 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-21 21:40:48 +0200jstolarek(~jstolarek@staticline-31-183-174-191.toya.net.pl) (Quit: Lost terminal)
2024-05-21 21:40:46 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-21 21:37:25 +0200mei(~mei@user/mei)
2024-05-21 21:34:59 +0200mei(~mei@user/mei) (Remote host closed the connection)
2024-05-21 21:34:57 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-21 21:34:57 +0200y04nn(~username@2a03:1b20:8:f011::e10d)
2024-05-21 21:33:32 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-21 21:27:30 +0200justsomeguy(~justsomeg@user/justsomeguy) (Read error: Connection reset by peer)
2024-05-21 21:27:18 +0200justsomeguy(~justsomeg@user/justsomeguy)
2024-05-21 21:26:22 +0200causal(~eric@50.35.88.207) (Quit: WeeChat 4.1.1)
2024-05-21 21:21:51 +0200tolt_tolt
2024-05-21 21:21:29 +0200mrmonday(~robert@what.i.hope.is.not.a.tabernaevagant.es)
2024-05-21 21:19:06 +0200mrmonday(~robert@what.i.hope.is.not.a.tabernaevagant.es) (Quit: .)
2024-05-21 21:18:20 +0200JimL(~quassel@89.162.16.26)
2024-05-21 21:17:59 +0200raehik(~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) (Ping timeout: 264 seconds)
2024-05-21 21:17:58 +0200JimL(~quassel@89.162.16.26) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
2024-05-21 21:17:23 +0200waleee(~waleee@h-176-10-144-38.NA.cust.bahnhof.se) (Ping timeout: 264 seconds)
2024-05-21 21:08:59 +0200Guest86(~Guest86@186.82.99.37) (Quit: Client closed)
2024-05-21 20:58:18 +0200 <EvanR> worker threads that can wait for work, furiously accomplish something and go back to sleep in ~0 time, vs the thread running the black hole merger simulation
2024-05-21 20:55:05 +0200mesaoptimizer(~mesaoptim@user/PapuaHardyNet)
2024-05-21 20:54:51 +0200mesaoptimizer(~mesaoptim@user/PapuaHardyNet) (Quit: mesaoptimizer)
2024-05-21 20:52:29 +0200yin(~yin@user/zero)
2024-05-21 20:50:40 +0200waleee(~waleee@h-176-10-144-38.NA.cust.bahnhof.se)
2024-05-21 20:50:01 +0200kuribas(~user@ptr-17d51encis8jg2ccf48.18120a2.ip6.access.telenet.be) (Remote host closed the connection)
2024-05-21 20:43:28 +0200ezzieyguywuf(~Unknown@user/ezzieyguywuf)
2024-05-21 20:42:39 +0200 <[exa]> like, most threads in existence just wait for some resource to arrive anyway, right
2024-05-21 20:42:38 +0200raehik(~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net)
2024-05-21 20:42:12 +0200 <dolio> Although I assume they weren't doing much.
2024-05-21 20:41:59 +0200 <dolio> There's an old ghc tracker ticker where Simon Marlow says he ran 1 million threads without a problem.
2024-05-21 20:41:24 +0200 <dolio> Yeah.
2024-05-21 20:41:02 +0200 <[exa]> dolio: btw the last time I read the RTS the total haskell IO-thread (_not_ OS thread) count was much more like memory-bounded than actually switch-starvation-bounded
2024-05-21 20:40:41 +0200Guest86(~Guest86@186.82.99.37)
2024-05-21 20:39:42 +0200 <mauke> (mind, this was a 32-bit system with limited RAM)
2024-05-21 20:39:09 +0200 <[exa]> let's take a moment now to commemorate the magnificent glorious 1 globally interpreter-locked thread of python