<< 04-06-2025 >>
00:31:22FromDiscord<nervecenter> Nope
01:17:44FromDiscord<janakali> In reply to @saint._._. "Do you know anyone": Apple
01:49:04*rockcavera joined #nim
02:30:27*xet7 joined #nim
03:06:15*rockcavera quit (Remote host closed the connection)
03:56:49*SchweinDeBurg joined #nim
04:39:09*m5zs7k_ joined #nim
04:39:28*m5zs7k quit (Read error: Connection reset by peer)
04:47:33*m5zs7k_ is now known as m5zs7k
06:15:23*maytham quit (Ping timeout: 245 seconds)
06:19:15*maytham joined #nim
08:52:21*xet7 quit (Remote host closed the connection)
09:23:30*andy-turner joined #nim
10:11:36*xet7 joined #nim
10:28:56*xet7 quit (Remote host closed the connection)
11:05:52*nils` quit (Ping timeout: 268 seconds)
12:28:17*nils` joined #nim
13:58:03*beholders_eye joined #nim
14:50:23*xet7 joined #nim
15:01:09*xet7 quit (Ping timeout: 248 seconds)
15:13:21*xet7 joined #nim
15:18:49FromDiscord<saint._._.> In reply to @janakali "Apple": What are they doing with it? For backend
15:26:31*amadaluzia joined #nim
15:47:07FromDiscord<janakali> In reply to @saint._._. "What are they doing": No one knows. But if they develop and maintain server-side framework like [swift-nio](https://github.com/apple/swift-nio) surely they use it for something, right?
16:24:59*beholders_eye quit (Ping timeout: 260 seconds)
16:43:36FromDiscord<nocturn9x> does anyone here have any experience with diagnosing performance problems in nim code
16:51:17*ntat joined #nim
16:54:41FromDiscord<Phil> Not beyond just looking at flamegraphs
16:54:52FromDiscord<Phil> Which makes it the same as performance-diagnosing C code
17:35:42*ntat quit (Quit: leaving)
17:36:17*SchweinDeBurg quit (Quit: WeeChat 4.7.0-dev)
18:08:12*ntat joined #nim
18:08:48*xet7 quit (Remote host closed the connection)
18:55:43*amadaluzia quit (Read error: Connection reset by peer)
18:55:54*amadaluzia_ joined #nim
19:47:40*przmk quit (Remote host closed the connection)
19:48:07*przmk joined #nim
19:51:39*amadaluzia_ quit (Ping timeout: 260 seconds)
20:01:40*amadaluzia joined #nim
20:13:24*przmk quit (Remote host closed the connection)
20:14:38*przmk joined #nim
20:20:35*przmk quit (Remote host closed the connection)
20:22:25*przmk joined #nim
20:32:22*skippy8 joined #nim
20:40:14*ntat quit (Quit: leaving)
21:30:35*andy-turner quit (Quit: Leaving)
21:35:42*rockcavera joined #nim
22:29:22*beholders_eye joined #nim
22:34:08*skippy8 quit (Quit: WeeChat 4.5.2)
22:44:21FromDiscord<user2m> has anyone figured out hot code reloading for something like a prologue app? I'm going crazy w/ compile times. most of my templates are server side so I'm recompiling for every little change
22:46:36FromDiscord<Robyn [She/Her]> In reply to @user2m "has anyone figured out": Not really, since it uses async, it's a bit more of a pain than i'd like it to be to even attempt HCR with it
22:50:07FromDiscord<Robyn [She/Her]> In reply to @user2m "has anyone figured out": A potential untested idea that could work is to make a shared library per whatever categorisation you wanna use, and in each dll, expose the set dispatcher function from https://nim-lang.org/docs/asyncdispatch.html#setGlobalDispatcher%2CsinkPDispatcher and then call that on every loaded DLL
22:50:15FromDiscord<Robyn [She/Her]> You also need to use Nim RTL
22:51:19FromDiscord<Robyn [She/Her]> @user2m
22:51:55*amadaluzia quit (Ping timeout: 252 seconds)
22:53:29*amadaluzia joined #nim
22:59:17FromDiscord<user2m> In reply to @battery.acid.bubblegum "A *potential* untested idea": Ooof. Just spent the past 2 days testing different ideas 😭
23:02:09FromDiscord<Robyn [She/Her]> In reply to @user2m "Ooof. Just spent the": What have you tried, out of curiousity?
23:08:05*beholders_eye quit (Ping timeout: 248 seconds)