<< 11-08-2026 >>

00:18:01*Skippy8 joined #nim
01:08:09*Vyrnexis joined #nim
01:18:03*Skippy8 quit (Ping timeout: 244 seconds)
03:05:38*SchweinDeBurg quit (Remote host closed the connection)
03:05:55*SchweinDeBurg joined #nim
05:04:49*SchweinDeBurg quit (Remote host closed the connection)
05:05:46*SchweinDeBurg joined #nim
07:24:38*tokyovigilante quit (Ping timeout: 265 seconds)
07:50:14*Skippy8 joined #nim
08:21:12*Skippy8 quit (Ping timeout: 244 seconds)
08:21:54*Skippy8 joined #nim
08:46:39FromDiscord<ryzh.> Is Nim's [HotCodeReload](https://nim-lang.github.io/Nim/hcr.html) incompatible with any Nim's [memory management strategies](https://nim-lang.org/docs/mm.html)?
08:47:22FromDiscord<ryzh.> (edit) "Is Nim's [HotCodeReload](https://nim-lang.github.io/Nim/hcr.html) incompatible with any ... Nim'smodels](https://nim-lang.org/docs/mm.html)?" added "of" | "strategies](https://nim-lang.org/docs/mm.html)?" => "models](https://nim-lang.org/docs/mm.html)?"
08:47:34FromDiscord<ryzh.> (edit) "[HotCodeReload](https://nim-lang.github.io/Nim/hcr.html)" => "[Hot Code Reloading](https://nim-lang.github.io/Nim/hcr.html)"
08:49:11*tokyovigilante joined #nim
09:19:22*Skippy8 quit (Ping timeout: 260 seconds)
09:25:49*Skippy8 joined #nim
09:36:37*Skippy8 quit (Ping timeout: 252 seconds)
10:01:22*beholders_eye joined #nim
10:15:14*sdothum quit (Remote host closed the connection)
10:17:56*sdothum joined #nim
10:30:10*Skippy8 joined #nim
10:47:55*Skippy8 quit (Ping timeout: 244 seconds)
10:52:56*Skippy8 joined #nim
10:57:55*Skippy8 quit (Ping timeout: 264 seconds)
11:00:41*Skippy8 joined #nim
11:12:25*Freneticks left #nim (#nim)
11:39:57*Skippy8 quit (Ping timeout: 260 seconds)
11:41:56*Skippy8 joined #nim
11:50:41*Skippy8 quit (Ping timeout: 250 seconds)
12:41:44*tokyovigilante quit (Ping timeout: 243 seconds)
12:42:42*xutaxkamay_ joined #nim
12:42:46*Lord_Nightmare2 joined #nim
12:43:00*xutaxkamay quit (Ping timeout: 245 seconds)
12:43:35*Lord_Nightmare quit (Ping timeout: 251 seconds)
12:43:43*xutaxkamay_ is now known as xutaxkamay
12:44:57*Lord_Nightmare2 is now known as Lord_Nightmare
12:52:08*Skippy8 joined #nim
13:12:20FromDiscord<ryzh.> well, ok, seems it's a [deprecated](https://discord.com/channels/371759389889003530/1414321156617535498/1462816881110028565) feature.
14:45:08*Skippy8 quit (Ping timeout: 268 seconds)
15:05:24FromDiscord<gesee37> @11clock I saw that in the past you wanted to have OOP in Nim. I just made this: https://github.com/Gesee-y/Nim-OOP↵↵It allow to have OOP like programming in Nim but in a fully static way
15:06:27FromDiscord<gesee37> It's probably the cleaniest code I ever wrote 🙂
15:32:42FromDiscord<11clock> In reply to @gesee37 "<@214055489057587211> I saw that": I have since changed my mind and have been learning data oriented programming.
15:32:55FromDiscord<11clock> Thanks though
15:33:41FromDiscord<11clock> Kept seeing big tech people talking about how bad OOP is so I am currently looking into why by doing data oriented programming myself.
15:34:12FromDiscord<11clock> Turned out much of my custom engine is already data oriented. The main challenge has been the game architecture itself.
15:39:24FromDiscord<gesee37> In reply to @11clock "I have since changed": Well it's also another way to structure an engine, even though I more a fan of data pipelines and frame graphs as they coordinate the frame while allowing both OOP and DOD to coexist
15:49:21FromDiscord<_timurski> In reply to @11clock "Kept seeing big tech": it's just about thinking "what are the actual ways to determine if code is good" and that is some sort of combination of runtime performance, compile time performance, code complexity, etc. then you just apply whatever makes the most sense
15:49:29FromDiscord<scoopahdoopah> we got oop at home
15:50:03FromDiscord<_timurski> compression oriented programming is a pretty interesting idea that i'm fond of that i think might be something LLMs can be pretty good at and be what allows them to write much better quality code on a larger scale
15:53:45FromDiscord<scoopahdoopah> the bad part of oop is just like behavior becoming tangled together so if you can avoid that you still want to be able to organize things as objects that communicate in some way
15:54:52FromDiscord<gesee37> In reply to @_timurski "it's just about thinking": A guy once told me that program can be all about the degree of materialization used in the program↵When expressivity and flexibility is the goal, we can keep a low degree of materialization (meaning less optimized for the material) while higher degree takes more and more the material into account while programming (which gives birth to DOD)
15:55:42FromDiscord<scoopahdoopah> the underlying data storage can still be huge tables
15:57:03FromDiscord<scoopahdoopah> and it should be cuz the underlying data storage is huge tables lmao