<< 10-03-2026 >>

00:42:25*nmz left #nim (Ploop)
01:57:55*Goodbye_Vincent1 quit (Ping timeout: 264 seconds)
02:02:22*beholders_eye quit (Ping timeout: 276 seconds)
02:05:38*mrinsane quit (Ping timeout: 252 seconds)
02:06:45*mrinsane joined #nim
02:48:55*mrinsane quit (Ping timeout: 245 seconds)
02:53:49*mrinsane joined #nim
02:55:10*mrinsane quit (Max SendQ exceeded)
02:55:38*mrinsane joined #nim
04:04:00*mrinsane quit (Ping timeout: 264 seconds)
04:04:51*mrinsane joined #nim
04:07:22*mrinsane quit (Max SendQ exceeded)
04:10:56*SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev)
04:12:39*mrinsane joined #nim
04:13:25*mrinsane quit (Max SendQ exceeded)
04:13:54*mrinsane joined #nim
04:14:33*mrinsane quit (Max SendQ exceeded)
04:16:23*mrinsane joined #nim
04:17:04*mrinsane quit (Max SendQ exceeded)
04:17:47*mrinsane joined #nim
04:22:57*mrinsane quit (Ping timeout: 246 seconds)
04:24:40*mrinsane joined #nim
04:25:05*SchweinDeBurg joined #nim
04:25:57*mrinsane quit (Max SendQ exceeded)
04:31:03*mrinsane joined #nim
04:33:27*Goodbye_Vincent1 joined #nim
05:28:18*mrinsane quit (Ping timeout: 248 seconds)
07:58:35*amadaluzia joined #nim
09:27:51FromDiscord<shalokshalom> In reply to @asviest "Does anyone have experience": GTK is normally quite poor in relationship to cross platform compatibilities, and looks ugly almost everywhere - except Gnome. ↵So yes, it looking bad and out of place in a Gnome environment, hints on an issue with the app itself.
09:28:32FromDiscord<shalokshalom> Did you see, that libdecor is 5 years out of date?
09:30:21*beholders_eye joined #nim
09:31:26FromDiscord<asviest> In reply to @shalokshalom "Did you see, that": No, it only about GitHub repo, actual repo on gitlab: https://gitlab.freedesktop.org/libdecor/libdecor/
09:34:08FromDiscord<asviest> In reply to @shalokshalom "GTK is normally quite": The problem lies elsewhere: the GTK plugin doesn't use libadwaita and looks non-native; plus, it's incredibly slow (the app freezes for several seconds when hovering over libdecor elements). Besides, this mainly concerns GNOME, as everything except Mutter supports server-side decorations.
10:21:57*rockcavera quit (Remote host closed the connection)
10:38:07*hygo joined #nim
11:16:05FromDiscord<asviest> In reply to @asviest "The problem lies elsewhere:": It works better with cairo plugin (it looks much more not native)
12:37:09*pmp-p quit (Ping timeout: 246 seconds)
12:39:44*pmp-p joined #nim
14:16:32*beholders_eye quit (Quit: WeeChat 4.8.2)
15:19:09*cm_ joined #nim
15:20:07*cm quit (Ping timeout: 264 seconds)
15:20:07*cm_ is now known as cm
15:46:12*mrinsane joined #nim
15:47:09*mrinsane quit (Max SendQ exceeded)
15:49:27*mrinsane joined #nim
15:50:18*mrinsane quit (Max SendQ exceeded)
15:52:14*mrinsane joined #nim
15:54:12*xet7 quit (Remote host closed the connection)
15:55:12*mrinsane_ joined #nim
15:57:07*mrinsane quit (Ping timeout: 248 seconds)
16:01:53*mrinsane joined #nim
16:04:36*mrinsane_ quit (Ping timeout: 264 seconds)
16:10:21*beholders_eye joined #nim
16:31:01*amadaluzia quit (Read error: Connection reset by peer)
16:46:44*beholders_eye quit (Ping timeout: 252 seconds)
17:25:04FromDiscord<indelusionalizationary> Is nim as fast as rust, c, cpp, as low level as them?
17:31:58FromDiscord<Buckwheat> Rust being on that list is kinda wild but Nim can sometimes hit the C/C++ speeds, I would argue Rust and C++ aren't really low-level, and I'd say Nim would be more high-level too semantically, but its binaries flatten very clean↵(@indelusionalizationary)
17:32:07FromDiscord<Buckwheat> I wouldn't be writing an OS or kernel in Nim though
17:33:55FromDiscord<asviest> In reply to @indelusionalizationary "Is nim as fast": I don't quite understand the point of the question; Nim is quite high-level, but the others are as well. You can achieve the speed of these programming languages, especially by using language features like {.cursor.} and others.
17:38:00FromDiscord<Buckwheat> worth mentioning if you're really trying to write super close to hardware, I think a lang like Nim (hell even Rust and C++) are a footgun because you need to have as clear of detail as possible, abstraction is bad there.
17:38:15FromDiscord<Buckwheat> and Nim is, really really abstracted
17:44:59FromDiscord<asviest> In reply to @asviest "I don't quite understand": https://nim-lang.org/docs/mm.html↵And for speed, it's better to use --mm:arc. For multithreading, there is --atomicArc, but it comes with some overhead (though it's minor). It simplifies multi-threading, but everything works great without it as well (just use locks, isolated, etc.).↵Check out: https://github.com/nim-lang/Nim/pull/21798
17:56:38FromDiscord<indelusionalizationary> In reply to @Buckwheat "I wouldn't be writing": why?
17:58:23FromDiscord<indelusionalizationary> I thought nim is systems programming language
17:59:58FromDiscord<tauruuuuuus> In reply to @Buckwheat "worth mentioning if you're": I routinely write nim for 8 bit microcontrollers, you just do not use ref types and you're mostly good