godot-nim VS karax

Since Godot 4 is gonna change their binding system the previous Nim bindings are not gonna work and the maintainers stated that they wont adapt the bindings to Godot 4.

Since Godot 4 is gonna change their binding system the previous [Nim bindings](https://github.com/pragmagic/godot-nim)

Another option is Nim. Looks and writes like Python but closer to C in performance. It also has static typing so I prefer it for scripting as well.

People have built a few games with the Nim Godot bindings:

https://github.com/pragmagic/godot-nim

There’s also an interesting project to do hot reloading using dlls:

https://github.com/geekrelief/gdnim

Enu is a 3D live-programming/learning/game development environment written in Nim using Godot 3, godot-nim, and godot_voxel. I use it to run a small local coding club with a group of 12 year olds, and think it is (or at least will be) a great tool for learning to code, and for making games quickly.

It uses a python-like language, is free & open-source (MIT License), has a fantastic GUI creation system, exports to all major OS's, and produces single small binaries. You could eventually incorporate Nim as well, as there are Nim bindings for Godot.

Ant then install the bindings. And thats where I'm a bit lost even after reading Godot docs. Not sure if I'm right, but seems to be necessary to compile Godot?

Well no language is perfect, but Nim can be used in almost every domain because of it's compilation targets(C, C++, JS) and it's fast compile times(who needs interpretation when compile times are that fast!):

* Shell scripting, I still assume most people will just use Bash tho: https://github.com/Vindaar/shell

* Frontend: https://github.com/karaxnim/karax or you could bind to an existing JS library.

* Backend: For something Flask-like: https://github.com/dom96/jester or something with more defaults https://github.com/planety/prologue

* Scientific computing: the wonderful SciNim https://github.com/SciNim

* Blockchain: Status has some of the biggest Nim codebases currently in production https://github.com/status-im?q=&type=&language=nim&sort=

* Gamedev: Also used in production: https://github.com/pragmagic/godot-nim and due to easy C and C++ interop, you get access to a lot of gamedev libraries!

* Embedded: this is a domain I know very little about but for example https://github.com/elcritch/nesper or https://github.com/PMunch/badger for fun Nim+embedded stuff!

Most of the disadvantages come from tooling and lack of $$$ support.

As for gdnim, it's my framework built on top of godot-nim. https://github.com/pragmagic/godot-nim https://github.com/pragmagic/godot-nim-stub

I've renewed my enjoyment of programming through game development (an area I haven't been active in before) and had a great time implementing a Quadtree in GDScript but then the other problem of raw execution speed for any script language made that a bit disappointing as well (it worked well but was only an improvement for larger numbers). So now I'm learning Nim (which has godot-nim bindings) to be able to write really performant code in an easy way.

The frontend uses Karax, which is my favorite frontend/SPA library. It is an absolute joy to use, even if it's a bit rough around the edges.

https://github.com/karaxnim/karax

I have used Nim for personal projects for 6 years now and it continues to surprise me on how well versed it is for many problem domains. I am fond of it's SPA framework, karax https://github.com/karaxnim/karax for which I wrote a translation utility https://github.com/nim-lang-cn/html2karax Latest Nimv2 release candidate has improved in the ergonomics and syntax that affect compilation to js, so I was able to cleanup my webapp's code to be less verbose. On GPU programming there has been a few projects that touch GPU programming, most notably https://github.com/treeform/shady

And it's present not only in Python but in other languages as well. Check for example https://github.com/karaxnim/karax - I don't know why people would want to hide all of their HTML in Python/whatever language. Then limit their ability to script and style it in one way or another.

> the real killer feature to me is the javascript target

Agree, this is amazing because you can share code and data structures between front and backend (for example: https://github.com/karaxnim/karax).

Also, it's really nice having high level stuff like metaprogramming and static typing spanning both targets. Things like reading a spec file and generating statically checked APIs for server/client is straightforward, which opens up a lot of possibilities.

E.g. Nim focuses on enabling what it calls "single page web apps": https://github.com/karaxnim/karax.

Karax [1] being Nim's SPA framework that also supports server side rendering.

[1]: https://github.com/karaxnim/karax

I recommend you to take a look at Karax. It's a front-end framework for Nim that can compile to regular JavaScript. If you want to know how to use it with a webserver, Joker is a good example. With the Joker config, all of the compiled .js files land in /public/views, where you can take a look at them. But keep in mind that the JS that Nim produces is often rather cumbersome and hundreds of lines long, even if it's just a simple program.