sdmac99

Crying garners attention from adults in either case. Any attention could be better than no attention I suppose.

I really need to thoroughly read this. I have scanned sections like the one on References and Pointers and found them useful, but only scratched the surface.

Late last year I switched my work site from Go to Nim. Then this year, with the help of the community and library nimterop, I was able to wrap the duckdb C api and use it in my web app for really fast analytic queries. I really like Nim syntax and the routes in jester:

  routes:
    get "/":
      resp "Wow, nice"

The false-positive virus issue affected my workstation as well, but after consulting with our security team we were able to resolve it.

I would love Nim to have more funding and support.

I like the batteries included approach, but certainly there are some libraries that do things like json better.

My experience with VR is that there is a period of acclimatization. At first it is tough to go 30min. I got up to being able to use it for an enjoyable 3 hours or at least the full duration of the battery for watching and gaming. I find when I come back from a long vacation with no screens, looking at a monitor for 7 hours is tough.

> Also, is anyone using Nim today?

Sure. I maintain an internal performance dashboard web app that is fully Nim. Backend uses Jester and the frontend uses Karax + Vega-lite for charts.

Check out this Nim talk. Addresses some of your questions.

https://www.youtube.com/watch?v=d2VRuZo2pdA

As a solo dev working in the public sector I recently moved to using Nim.

Backend: Jester (Nim) Front-end: Karax (Nim) Db: sqlite/mariadb Host: digital ocean

I find that I can implement features much faster and with less code compared to my previous Go/Js stack.

duckdb is another good option as well.

I would like it if Vaex was added to the benchmarks.