<< 20-08-2025 >>
00:00:44*xet7 quit (Remote host closed the connection)
00:02:04*xet7 joined #nim
00:06:40*fallback quit (Server closed connection)
00:21:59*fallback joined #nim
00:54:33*cornfeedhobo quit (Ping timeout: 245 seconds)
01:00:44*xet7 quit (Remote host closed the connection)
01:10:08*cornfeedhobo_ joined #nim
01:21:50*cornfeedhobo_ is now known as cornfeedhobo
01:48:17*rockcavera quit (Remote host closed the connection)
02:35:02*CypherCat quit (Remote host closed the connection)
02:35:24*ttydes quit (Ping timeout: 252 seconds)
02:39:40*ttydes joined #nim
02:43:26*CypherCat joined #nim
03:20:02*CypherCat quit (Remote host closed the connection)
03:23:15*CypherCat joined #nim
03:26:53*Lord_Nightmare quit (Server closed connection)
03:27:10*Lord_Nightmare joined #nim
05:28:45*skippy8 joined #nim
05:52:54*derpydoo joined #nim
06:43:08*beholders_eye joined #nim
06:49:49*beholders_eye quit (Ping timeout: 256 seconds)
07:15:16*jjido joined #nim
07:17:18FromDiscord<that_dude.> sent a code paste, see https://play.nim-lang.org/#pasty=LvCQfrUJ
07:17:46FromDiscord<that_dude.> Any thoughts on what I could be looking for?
07:19:19*SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev)
07:19:49*SchweinDeBurg joined #nim
07:43:52*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
07:49:09FromDiscord<leorize> add `-d:useMalloc` and `--gc:arc`
07:49:22FromDiscord<leorize> `--mm:arc`, I mean
07:50:03FromDiscord<leorize> `--mm:atomicArc`, I mean
08:06:42*redj quit (Ping timeout: 260 seconds)
08:14:22*redj joined #nim
08:15:37*jjido joined #nim
08:23:44*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
08:32:11*xet7 joined #nim
08:33:43*amadaluzia joined #nim
08:38:28*xet7 quit (Remote host closed the connection)
08:39:50*xet7 joined #nim
08:43:47*jjido joined #nim
08:47:48*amadaluzia quit (Quit: ZNC 1.9.1 - https://znc.in)
08:52:33*amadaluzia joined #nim
08:53:14*amadaluzia quit (Remote host closed the connection)
08:55:15*amadaluzia joined #nim
08:55:46FromDiscord<albassort> In reply to @blashyrk "Yes. Alternatively you can": Soviet Nim has no private identifiers
08:57:02FromDiscord<albassort> In Soviet Nim dependency imports you! (but thats more like forth or lisp or smth)
08:58:39*derpydoo quit (Quit: derpydoo)
09:02:45*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
09:05:20Amun-Rasoviet nim should've stalin sort implemented in stdlib
09:15:37FromDiscord<albassort> stalin sort is kinda not efficient because the output array is of unkown size and would need realloc to compensate for lost size
09:15:38FromDiscord<albassort> >:(
09:28:43*jjido joined #nim
09:34:35Amun-Rastalin doesn't care about your feelings ;)
09:35:04Amun-Rajust store the array length in a separate place
09:38:35FromDiscord<0xfab_10> linked list
09:45:09*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
09:50:33*amadaluzia quit (Quit: ZNC 1.9.1 - https://znc.in)
09:50:56*amadaluzia joined #nim
10:18:15*xtr00 quit (Read error: Connection reset by peer)
10:20:28Amun-Rachained list in that case ;)
10:22:16*xtr00 joined #nim
10:43:17*xtr00 quit (Ping timeout: 256 seconds)
10:49:08*xtr00 joined #nim
10:54:23*amadaluzia quit (Quit: ZNC 1.9.1 - https://znc.in)
11:00:15*nils` quit (Ping timeout: 260 seconds)
11:06:16FromDiscord<aintea> Why in the world is my non threaded code faster when compiled with `-d:ThreadPoolSize=12 -d:FixedChanSize=16`
11:06:34FromDiscord<aintea> and why is it even faster than my actually threaded version of the code
11:06:46FromDiscord<aintea> that's it I'm becoming a farmer
11:06:49*xtr00 quit (Read error: Connection reset by peer)
11:09:21*xtr00 joined #nim
11:18:11*xtr00 quit (Read error: Connection reset by peer)
11:19:48*xtr00 joined #nim
11:52:23*amadaluzia joined #nim
12:05:24*xtr00 quit (Read error: Connection reset by peer)
12:08:47*xtr00 joined #nim
12:28:33FromDiscord<janakali> In reply to @aintea "Why in the world": Are those even real? I can only find `MaxThreadPoolSize` in std↵Also, threading is hard and it's a common problem that parallelism often results in slower performance unless there is a significant amount of highly parallelizable work.
12:29:21*nils` joined #nim
12:33:07FromDiscord<lainlaylie> I think those are malebolgia flags
12:44:44FromDiscord<aintea> Yes
12:45:05FromDiscord<aintea> It speeds up a program where I don't even use malebolgia
12:45:18FromDiscord<aintea> From 2.9s to 0.9 or something like it
13:05:02*xet7 quit (Ping timeout: 272 seconds)
13:05:26*xet7 joined #nim
13:11:11*xet7 quit (Remote host closed the connection)
13:13:25*beholders_eye joined #nim
13:21:54FromDiscord<0xfab_10> threading is slow if you're not using a thread pool and have jank work scheduling
13:50:44*skippy8 quit (Quit: WeeChat 4.7.0)
13:52:02*jjido joined #nim
14:00:39FromDiscord<albassort> In reply to @fabric.input_output "threading is slow if": not rank!
14:00:44FromDiscord<albassort> (edit) "rank!" => "jank!"
14:01:11FromDiscord<albassort> but yes threads are slow, they are individual processes being created in a hirearchy.
14:01:29FromDiscord<albassort> and remember, IPC is also slow, slower than just executing stuff
14:01:46FromDiscord<0xfab_10> threads share memory
14:01:54FromDiscord<albassort> yeah but they're processes
14:01:58FromDiscord<albassort> also not always
14:02:00FromDiscord<0xfab_10> not exactly
14:02:03FromDiscord<albassort> ehhh
14:02:06FromDiscord<albassort> close enough
14:02:11FromDiscord<0xfab_10> nah
14:02:34FromDiscord<Robyn [She/Her]> processes and threads are different, no? threads run under a single process
14:02:36FromDiscord<0xfab_10> only overhead threads have is making them
14:02:46FromDiscord<0xfab_10> also sync too probs
14:03:04FromDiscord<0xfab_10> (edit) "making" => "starting"
14:03:07FromDiscord<Robyn [She/Her]> Python using multiprocessing rather than multithreading bc of this, the GIL is per process
14:03:42FromDiscord<0xfab_10> I think they're removing it
14:03:48FromDiscord<albassort> In reply to @battery.acid.bubblegum "processes and threads are": apparently threads as processes is old misinformation :3
14:03:53FromDiscord<Robyn [She/Her]> they said that back in 3.11 lel
14:04:05FromDiscord<Robyn [She/Her]> In reply to @albassort "apparently threads as processes": oof
14:04:37FromDiscord<albassort> its not been that way outside of python since before i was born :3
14:04:42FromDiscord<albassort> 2001
14:04:53FromDiscord<Robyn [She/Her]> wdym not been that waym
14:04:54FromDiscord<Robyn [She/Her]> ?
14:04:56FromDiscord<albassort> apologies for the misinformation
14:05:01FromDiscord<albassort> originally threads had PIDs
14:05:04*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
14:05:15*andy-turner joined #nim
14:05:24FromDiscord<Robyn [She/Her]> all good dw girlie
14:05:36FromDiscord<Robyn [She/Her]> In reply to @albassort "originally threads had PIDs": huh, which OS had that?
14:05:55FromDiscord<albassort> sent a code paste, see https://play.nim-lang.org/#pasty=xTNAHuyk
14:06:00FromDiscord<albassort> In reply to @battery.acid.bubblegum "huh, which OS had": linux
14:06:10FromDiscord<albassort> so no sharing smart pointers and channels and such is not IPC
14:06:13FromDiscord<albassort> im big dumb sorr
14:06:15FromDiscord<albassort> (edit) "sorr" => "sorry :3"
14:06:22FromDiscord<leorize> share memory, in nim? you gotta be kidding
14:06:30FromDiscord<albassort> we got a shared block
14:06:37FromDiscord<albassort> createShared ;3
14:06:46FromDiscord<albassort> dont tell anyone tho
14:06:49FromDiscord<albassort> they might use it wrong
14:07:02FromDiscord<Robyn [She/Her]> bridge is dropping stuff, it's catching up
14:07:14FromDiscord<0xfab_10> >be araq↵>"I don't like erlang share-by-copying-messages"↵>sharing sucks↵>people share by deep copying messages
14:07:20FromDiscord<0xfab_10> how accurate is this
14:07:55FromDiscord<albassort> its not as bad as CPP sharing with smart pointers and such
14:07:59FromDiscord<0xfab_10> In reply to @albassort "they might use it": just make your own `Arc[T]` like the one in rust and don't use `ref`s, ezpz
14:08:19FromDiscord<0xfab_10> backed by createShared
14:08:38FromDiscord<albassort> Rust
14:08:48FromDiscord<albassort> i fear no man
14:08:50FromDiscord<albassort> but that thing
14:10:23*nils` quit (Ping timeout: 245 seconds)
14:10:38FromDiscord<0xfab_10> rust is fun
14:10:46FromDiscord<albassort> rust is slow and kinda ugly
14:10:47FromDiscord<0xfab_10> wish there was smth like rust with gc
14:10:50FromDiscord<albassort> slow to compile
14:11:32FromDiscord<0xfab_10> eh I've been desensitized by c++ to think rust is ugly
14:11:43FromDiscord<0xfab_10> never wanna touch c++ again
14:11:50FromDiscord<0xfab_10> shiver me timbers
14:11:50FromDiscord<albassort> C++ is hideous
14:11:57FromDiscord<albassort> C is kinda pretty
14:12:20FromDiscord<0xfab_10> C is mid imo, it is ugly but not a deal breaker
14:12:54FromDiscord<0xfab_10> zig strikes a special ugly nerve
14:12:59FromDiscord<albassort> i am highkey at a point where I think that, we should like just agree on something and keep it dogma
14:13:04FromDiscord<albassort> and just dogma people into using it
14:13:17FromDiscord<albassort> and like just never acknowledge anything else
14:13:21FromDiscord<albassort> make it a religion or something
14:13:42FromDiscord<albassort> (edit) "i am highkey at a point where I think that, we should like just agree on something and keep it ... dogma" added "as"
14:14:52FromDiscord<albassort> thats why in the future i will only be making emotional arguments for Nim and C by saying and claim that they are contingent concepts to the universe and evidence of a higher creater
14:15:21FromDiscord<albassort> (edit) "by saying and claim" => "claiming"
14:17:22FromDiscord<0xfab_10> cmon we all know god wrote the universe in lisp
14:17:44FromDiscord<albassort> Forth
14:19:06FromDiscord<0xfab_10> forth parser for nim compiler called north
14:19:28FromDiscord<albassort> like we build a forth just around parsing the nim compiler
14:19:38FromDiscord<albassort> so it like mutates the compiler and the nim at runtime
14:19:59FromDiscord<albassort> could maybe be done with NLVM?
14:20:12FromDiscord<albassort> but like a LLVM level forth is kinda... idk if thats possible
14:30:14*beholders_eye quit (Ping timeout: 260 seconds)
14:38:46*xtr00 quit (Read error: Connection reset by peer)
14:44:32*xtr00 joined #nim
15:00:34*nils` joined #nim
15:25:21FromDiscord<janakali> In reply to @fabric.input_output "cmon we all know": Paul Graham originally wrote universe, in lisp, on the back of a napkin while he was waiting for a coffee.
15:34:01*beholders_eye joined #nim
15:44:33*beholders_eye quit (Ping timeout: 276 seconds)
15:44:51FromDiscord<0xfab_10> not a fan of that guy
16:01:32*zgasma joined #nim
16:06:49*ehmry quit (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)
16:10:01*ehmry joined #nim
16:12:42*andy-turner quit (Quit: Leaving)
16:19:52*amadaluzia quit (Quit: ZNC 1.9.1 - https://znc.in)
16:20:09*amadaluzia joined #nim
17:56:45*skippy8 joined #nim
18:10:44*nils` quit (Ping timeout: 244 seconds)
18:39:35FromDiscord<aintea> In reply to @fabric.input_output "threading is slow if": That's the whole problem, it's slow when I'm using one and fast when I'm not using one
18:55:06*jjido joined #nim
19:20:57FromDiscord<heysokam> In reply to @aintea "That's the whole problem,": Sending work to a scheduler has costs↵If your work is not hard enough to churn, then the overhead of multi-threading it will make it slower overall
19:38:15*nils` joined #nim
19:40:25*ttydes quit (Remote host closed the connection)
19:41:30*ttydes joined #nim
19:55:22*skippy8 quit (Quit: WeeChat 4.7.0)
20:06:13*xtr00 quit (Ping timeout: 245 seconds)
20:06:41*xtr00 joined #nim
20:22:02FromDiscord<0xfab_10> you're just pushing to a work queue. not that much of a cost
20:26:22*xet7 joined #nim
20:31:07*xtr00 quit (Ping timeout: 255 seconds)
20:35:18*xtr00 joined #nim
20:40:05*skippy8 joined #nim
21:21:05*jjido quit (Quit: My laptop has gone to sleep. ZZZzzz…)
21:25:08*buho joined #nim
21:29:27FromDiscord<ollicron_53732> I'm re-inventing the wheel
21:29:36*buho left #nim (#nim)
21:29:54FromDiscord<ollicron_53732> I couldn't help myself u.u as a result I made the output 3x faster than the original
21:32:18FromDiscord<sebastian_valmont> What's the easiest way for me to write an app that can detect key down, key hold, key up ? It has to work cross platform
21:45:17FromDiscord<nasuray> In reply to @sebastian_valmont "What's the easiest way": For what? Sounds nefarious
21:48:01*beholders_eye joined #nim
21:54:35*skippy8 quit (Quit: WeeChat 4.7.0)
22:03:07*rockcavera joined #nim
22:11:13*beholders_eye quit (Ping timeout: 256 seconds)
22:31:34FromDiscord<tsoj> sent a code paste, see https://play.nim-lang.org/#pasty=nZMIaOjK
22:41:02FromDiscord<Elegantbeef> Nim compiler bug likely given removing wasmoved stops it
23:31:18*xet7 quit (Remote host closed the connection)
23:56:30*GnuYawk1 quit (Quit: The Lounge - https://thelounge.chat)