| 00:01:02 | FromDiscord | <sunpoke04> okay, I think nim is not a good choice for this :d https://media.discordapp.net/attachments/371759389889003532/1424546960391540928/image.png?ex=68e4583e&is=68e306be&hm=c86bd4107aa9ef8d39238ec9357b93b873fca1c539c381e171bb19ff583c14ec& |
| 00:07:22 | * | Mister_Magister quit (Quit: bye) |
| 00:09:56 | * | Mister_Magister joined #nim |
| 00:28:22 | FromDiscord | <nervecenter> In reply to @sunpoke04 "okay, I think nim": Use Nimja templates |
| 00:29:12 | FromDiscord | <nervecenter> Make procs that take all the parameters, pass them to the templates. They're actual Nim templates that generate at compile time, so they'll be built into your final source. |
| 00:30:06 | FromDiscord | <nervecenter> And the nimja files are just HTML with some extra parameter-injection and conditional syntax on top |
| 00:39:38 | FromDiscord | <sunpoke04> In reply to @nervecenter "Use Nimja templates": that wouldn't fix the js problem though |
| 01:14:17 | FromDiscord | <nervecenter> nothing can fix the JS problem |
| 02:00:05 | FromDiscord | <sunpoke04> In reply to @nervecenter "nothing can fix the": maybe more js can fix the problem - js devs |
| 02:28:08 | * | xtr00 quit (Ping timeout: 256 seconds) |
| 03:26:11 | * | xtr00 joined #nim |
| 04:41:33 | * | lx12ucy quit (Remote host closed the connection) |
| 06:27:35 | * | SchweinDeBurg quit (Quit: WeeChat 4.8.0-dev) |
| 06:28:02 | * | SchweinDeBurg joined #nim |
| 06:56:40 | * | xtr00_ joined #nim |
| 06:58:23 | * | xtr00 quit (*.net *.split) |
| 06:58:24 | * | kasimir_ quit (*.net *.split) |
| 06:58:25 | * | Goodbye_Vincent1 quit (*.net *.split) |
| 07:01:14 | * | kasimir_ joined #nim |
| 07:01:14 | * | Goodbye_Vincent1 joined #nim |
| 08:02:48 | * | beholders_eye joined #nim |
| 08:11:03 | FromDiscord | <tearsinrain__> are there standard vector math packages similar to numpy in nim or i should just use nimpy bindings |
| 08:22:09 | FromDiscord | <lainlaylie> i think stuff like arraymancer and vmath |
| 08:56:14 | FromDiscord | <_.elias._> In reply to @tearsinrain__ "im building some high": Hi!, I write all my trading bots in Nim, relying heavily on the language’s async/await infrastructure.↵After long-running sessions I routinely hit the “too many open file descriptors” ceiling, so I am evaluating a future move to Chronos (the purely async runtime used by the Nim compiler itself) in the hope of eliminating that resource leak. Despite that the experience is very |
| 08:59:21 | FromDiscord | <ieltan> I dont think the nim compiler uses chronos 🤔 |
| 08:59:35 | FromDiscord | <ieltan> https://github.com/status-im/nim-chronos |
| 09:02:31 | FromDiscord | <tearsinrain__> In reply to @_.elias._ "Hi!, I write all": hmm. would love to chat. im coming from python as well and have deep experience in it. im wondering about why you're hitting that issue and if its just sockets / ipc being opened or what |
| 09:04:59 | FromDiscord | <ieltan> asyncdispatch has all kinds of subtle issues unfortunately he's probably hitting one of leaking bugs plaguing it |
| 09:06:44 | FromDiscord | <ieltan> sounds like the program is not properly releasing file descriptors so they accumulate until the OS kills it |
| 09:07:39 | FromDiscord | <mitranim> In reply to @sunpoke04 "okay, I think nim": Maybe you want the Karax library |
| 09:09:27 | FromDiscord | <ieltan> btw it may not even be asyncdispatch fault and might just be the code itself :p |
| 09:10:50 | FromDiscord | <tearsinrain__> In reply to @ieltan "sounds like the program": right |
| 09:11:13 | FromDiscord | <tearsinrain__> but then a lot of sockets must be opened and closed rather than a few long running connections as well |
| 09:11:36 | FromDiscord | <tearsinrain__> so im wondering if its an engineering thing i can work around, something to be careful of (socket lifecycle management), or an actual problem with the library |
| 09:12:48 | * | anddam quit (*.net *.split) |
| 09:12:48 | * | computerquip quit (*.net *.split) |
| 09:12:49 | * | przmk quit (*.net *.split) |
| 09:12:49 | * | mal`` quit (*.net *.split) |
| 09:12:49 | * | attah quit (*.net *.split) |
| 09:12:49 | * | mahlon quit (*.net *.split) |
| 09:14:21 | * | anddam joined #nim |
| 09:14:21 | * | computerquip joined #nim |
| 09:14:21 | * | przmk joined #nim |
| 09:14:21 | * | mal`` joined #nim |
| 09:14:21 | * | attah joined #nim |
| 09:14:21 | * | mahlon joined #nim |
| 09:16:39 | * | computerquip quit (Ping timeout: 244 seconds) |
| 09:17:23 | * | computerquip joined #nim |
| 09:21:02 | FromDiscord | <0xfab_10> In reply to @_.elias._ "Hi!, I write all": > too many open file descriptors↵that's usually an OS limit thing. you can configure that limit. refer https://www.cogini.com/blog/tuning-tcp-ports-for-your-elixir-app/ (elixir because that's the one I had). has some links to other resources |
| 09:21:45 | FromDiscord | <0xfab_10> assuming you're properly handling all your file descriptors that is |
| 09:21:53 | FromDiscord | <0xfab_10> so you might wanna check for a leak first |
