4 ms·
I had previously added Nim stdlib to the techempower benchmarks as I wanted to better understand what is it that Nim lacks from a webdev perspective. That exer
by rishav_sharan 5y ago
I had previously added Nim stdlib to the techempower benchmarks as I wanted to better understand what is it that Nim lacks from a webdev perspective.
That exerciise taught me that, more than anything else, Nim needs good DB drivers with async support. The current driver are terrible and are the main reason why Nim is practically useless for web dev.
The language itself is fine. the std lib supports creating simple web projects without using any framework at all. All the maintainers need to focus on is good connectivity to the dbs. For postgres, even wrapping libpq would be a great start.
- cyber_kinetist 5y agoThe more desperate thing that Nim currently needs is better tooling to create bindings for C libraries. c2nim fails to work in a lot of cases, and nimterop still needs a bit more work.
- anaphor 5y agoYou can always call the C functions directly (from a shared lib) although admittedly it's a pain because you have to deal with unmanaged pointers very often.
- dom96 5y ago> The current driver are terrible and are the main reason why Nim is practically useless for web dev. As biased as I am I strongly disagree. You can get really far with the db drivers that are in the stdlib (the Nim Forum works very well with just db_sqlite which IMO disproves that Nim is useless for web dev). For something more advanced we need somebody who likes working on these kinds of things to write up a few amazing async db drivers in Nim :)
- rishav_sharan 5y agoHey Dom. I realise that my tone of commenting was unnecessarily hostile. I apologise about that. I love nim and wish the best to it, but I think you will also agree that an async driver for databases like PG are the lowest and ripest hanging fruits to take nim webdev to the next level.