ThomasTJdev

5 ms·

1. 1.▲
   by ThomasTJdev 11mo ago

   Nice! Nim has been great for us - fast to code in and even faster once compiled! We're using it for the backend and microservices at https://cxplanner.com and loving it.
2. 2.▲
   by ThomasTJdev 3y ago

   Nim-lang fits 1, 2 and 3! And in a couple of years the ecosystem is up to level ;)
3. 3.▲
   by ThomasTJdev 3y ago

   One of the reasons for choosing Nim was the ease of getting a production ready web backend. For the core part of managing the backend we are using existing Nim libraries [1], and they are easy to expand and work with. I cannot give you a co
4. 4.▲
   by ThomasTJdev 3y ago

   For startups, you can count us in[1]. Our backend, across all services, is using Nim. [1] https://cxplanner.com
5. 5.▲
   by ThomasTJdev 3y ago

   Have a look at Jackson from https://boxyhq.com . Spin up one container and a couple of simple endpoints - voila, up and running. And a really cool team too!
6. 6.▲
   by ThomasTJdev 3y ago

   A full project management platform for construction projects. Webserver, websocket, microservices, etc.: https://cxplanner.com
7. 7.▲
   by ThomasTJdev 3y ago

   Ditto! Nim is just easy and incredibly fast (to develop and the code!). Our code base is Nim based - even normal bash script have been replaced!
8. 8.▲
   by ThomasTJdev 4y ago

   We use it at www.cxplanner.com for a mix of micro/mono-services. Statically typed and good compile time combined with really fast code makes Nim perfect for us.
9. 9.▲
   by ThomasTJdev 4y ago

   For me it was. Python was everything for me - but too slow. It was a pretty quick to convert software to Nim, and I have never looked back. You don't get the whole ecosystem from python, but you get fast code and easy syntax. We even o
10. 10.▲
    by ThomasTJdev 5y ago

    I don’t know about other web-guides. Nim’s official website is made with Nim and available at Github[0], but it has become at bit more complicated after they switched to Karax[1]. Jester’s tests gives a good view on the routing procedures[2
11. 11.▲
    by ThomasTJdev 5y ago

    I'm glad you liked it! We have been using Nim from 0.18.x to now (1.6.x) with a minimal work with breaking changes - so no warning signals from here. My advice would be to use the current stable version since 2.0.0 is just around the c
12. 12.▲
    by ThomasTJdev 5y ago

    [Author here] This post was quite a surprise to see here! Guess who got busy checking out his old repository ;) . This is a blog post from 2019 during my Nim journey, which has now resulted in our entire SaaS[0] running Nim. Nim[1] has evol