Nim Days Chapter 21: Parser combinators and Nim

Here's a new chapter for one of my earliest code in nim nim-parsec [https://xmonader.github.io/nimdays/day21_parsec.html](https://xmonader.github.io/nimdays/day21_parsec.html)

Re: Nimble Directory Redesign

Looks nice indeed, is there a possibility to make the searchbox stands out bit more? I couldn't recognize it easily

Re: How mature is async/threading in Nim?

Adding to that [https://github.com/nim-lang/Nim/issues/14429](https://github.com/nim-lang/Nim/issues/14429) :)

Re: Faster and Safer Raytracing in Nim

@mratsim it's always a pleasure to see your posts and work :) thank you

Nim Days Progress

I added two more chapters on wit.ai client and creating a CacheTable. I hope you guys find it useful :) Now Nim days reached 20 chapters in total. thank you everyone for your kind responses and valuable input

Re: Another micro web framework Prologue

That's such a great job! looks like I'll have to put some effort in nim-servy to keep some competition :)

Re: Pipe operator in Nim

because of ufcs you can use . e.g a.echo

Re: Jester: How to serve static files in production (Heroku)?

You can use nimassets and stop worrying about bundling static files :) [https://github.com/xmonader/nimassets](https://github.com/xmonader/nimassets)

Re: build*.exe with pictures, icons...

yeah, the idea of nimassets is compiling all of your assets into a nim file that will be compiled as part of your executable (check its mechanism here [https://xmonader.github.io/nimdays/day14_nimassets.html](https://xmonader.github.io/nimdays/day14_nimassets.html))

Re: build*.exe with pictures, icons...

I encourage you to give nimassets a try [https://github.com/xmonader/nimassets](https://github.com/xmonader/nimassets)

Day18 From a socket to webframework

Here we go with another day on writing a webframework starting with a socket in nim [https://xmonader.github.io/nimdays/day18_webframework.html](https://xmonader.github.io/nimdays/day18_webframework.html)

Re: query pc specification?

lscpu, lspci, lshw, lsblk, ... rest of ls family or use dmidecode and pass the output to nim-dmidecode [https://github.com/xmonader/nim-dmidecode](https://github.com/xmonader/nim-dmidecode)

Re: nimble task arguments

yes [https://github.com/nim-lang/nimble/issues/633](https://github.com/nim-lang/nimble/issues/633)

Re: Nim Days: Day 17 Building Sonic Client in Nim

I appreciate your words. Hopefully, I can get more chapters coming. btw, I love dom's work! it's well written and has lots of clear explanations and I think both books can complement each other

Nim Days: Day 17 Building Sonic Client in Nim

It's one of the projects I never documented [https://xmonader.github.io/nimdays/day17_nimsonicclient.html](https://xmonader.github.io/nimdays/day17_nimsonicclient.html) there's a space for improvement including utilizing a connection pool (I've already implemented that in python) if any takers.

Re: Gintro gtk_builder_new_from_string

you can use nimassets to distribute the xml resource file a long [https://github.com/xmonader/nimassets](https://github.com/xmonader/nimassets)

Re: Great tutorials needed

Thank you! Also, It used to be under the books section before, but now in its position it will be overlooked most likely :)

Re: Great tutorials needed

I encourage you to check my Nim days book [https://xmonader.github.io/nimdays](https://xmonader.github.io/nimdays)/ basically you will follow the steps for * ini parser * bencode parser * links checker * tictactoe (commandline and gui) * testing framework * build system * tcp route

Re: Call to all nimble package authors

Code/Doc quality is a must indeed, but I refuse to be part of some biased unclear scoring system that threatens to remove my packages I'm doing so in my free time _NOT PAID_ because of unclear process. code_quality - (Optional) An integer evaluation of code quality between 1 (low)

Re: What prevents you from using Nim as your main programming language?

I'd say immature libraries, you're going to a complete ecosystem not just the language. Looking back at [https://xmonader.github.io/nim/2018/12/06/nim-good-ok-hard.html](https://xmonader.github.io/nim/2018/12/06/nim-good-ok-hard.html) I find there're lots of improvements like lots of effort on d

Re: Nim Days progress

Thank you! I'm happy you think that way :) I'm update it the code when I can ^_^

Re: Nim Days progress

Hope it helps people with Nim :) I'll try updating the book as soon as possible. Thank you

Re: Nim Days progress

Thank you!

Nim Days progress

today I added two chapters tcp forwarder and terminaltables :) I hope the book helps you with your Nim journey [https://xmonader.github.io/nimdays](https://xmonader.github.io/nimdays)/ and please feel free to open issue or create PR to improve/fix :)

nim-terminaltables

[terminaltables](https://github.com/xmonader/nim-terminaltables) is used to generate terminal tables (ascii or unicode ones) with customizable styles there're some examples in the repo ^_^ Please feel free to open issues or contribute in any suitable way, maybe even better choice for the charac

Re: Need help with creating a module featuring asynchronous access of Redis

You need to call your async proc with waitFor e.g [https://github.com/xmonader/nim-redisclient/blob/master/tests/testredisclient.nim](https://github.com/xmonader/nim-redisclient/blob/master/tests/testredisclient.nim)

Re: "Nim needs better documentation" - share your thoughts

Hi! Thanks for listening to the community and Good luck @miran (and everyone) in making nim better! Documentation can be classified into * Soft documentation (clean examples, tutorials how to do X, or building applications e2e this is a major factor) * Hard (reference) documentation (docume