denim
sokol-zig
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
denim
-
My Node.js is a bit Rusty
Related: you can write a Node.js module in Nim with Denim: https://github.com/openpeeps/denim
-
Nim v2.0 Released
Somewhat related, you can call Nim code from Node.js/Bun using Denim: https://github.com/openpeeps/denim. It works by creating a Node add-on.
This is great for reusing Nim code in a web app, and possibly for performance critical code.
-
Node vs Flask for Scaling
Something I'm just starting for one of my projects, is to use Node on front-end and back-end (mostly for GraphQL). Then write the majority of the back-end in Nim and compile it to a Node add-on with Denim (https://github.com/openpeeps/denim). Nim can call Python with Nimpy if I ever need to call it.
sokol-zig
-
Zig cookbook: collection of simple Zig programs that demonstrate good practices
Zig currently doesn't allow chained designators and also doesn't allow to partially initialize arrays and fill up the rest of the array with default values.
E.g. the closest Zig equivalent to this C99 code:
https://github.com/floooh/sokol-samples/blob/b3bc55c4411fa03...
...is this:
https://github.com/floooh/sokol-zig/blob/a4b3c287fadd153a504...
...note how part of the initialization had to be moved out into "code".
There's a ticket about this here, but it's currently not high-priority:
https://github.com/ziglang/zig/issues/6068
-
Nim v2.0 Released
I maintain auto-generated bindings for my C libraries for Zig and Nim (and Odin and Rust - although the Rust bindings definitely need some love to make them a lot more idiomatic).
I think looking at the examples (which is essentially the same code in different languages) gives you a high level idea, but they only scratch the surface when it comes to language features (things like the Zig code not using comptime features):
Zig: https://github.com/floooh/sokol-zig/tree/master/src/examples
Nim: https://github.com/floooh/sokol-nim/tree/master/examples
Odin: https://github.com/floooh/sokol-odin/tree/main/examples
Rust: https://github.com/floooh/sokol-rust/tree/main/examples
-
Zig Build System
IMHO you really need a programming language to describe a build, even when the result looks very declarative.
E.g. not sure how Meson handles this, but when I have a project with dozens of similar build targets and platform specific compile options, I really want to do the build description in a loop instead of a data tree.
(for example: https://github.com/floooh/sokol-zig/blob/3f978e58712f9eb029b...)
- Zig and WASM
-
Mach v0.1 - cross-platform Zig graphics in ~60 seconds
Is this project comparable to the zig sokol project?https://github.com/floooh/sokol-zig
-
How does zig magically cross compile without target shared libraries
I was rather amazed that I could cross-compile the zig-sokol examples https://github.com/floooh/sokol-zig for a Windows target on a Linux host (WSL Ubuntu). I simply set -target x86_64-windows and copied the executable into Windows and got a nice spinning cube displayed.
-
Mach Engine: The Future of Graphics (With Zig)
(disclaimer: shameless plug) Here's another cross-platform alternative, auto-generated Zig bindings to the Sokol headers:
https://github.com/floooh/sokol-zig
This is quite a bit slimmer than using one of the WebGPU libraries like wgpu-rs or Dawn, because sokol-gfx doesn't need an integrated shader cross-compiler (instead translation from a common shader source to the backend-specific shader formats happens offline).
Eventually I'd also like to support the Android, iOS and WASM backends from Zig (currently this only works from C/C++, for instance here are the WASM demos: https://floooh.github.io/sokol-html5/)
-
Making Win32 APIs More Accessible to More Languages
I'm tackling this issue from two sides:
(1) Change the C-API to make it more "binding-generator-friendly", for instance by adding a range/slice-struct to th C-API which bundles a pointer and associated size, or specially named typedefs that only exist to give the binding generator hints for special case handling.
(2) Make the bindings-generator configurable on a per-language and per-API basis, this can be as simple as a map which overrides type- and function-names, or injects manually written code into the generated bindings.
The goal is to make the generated bindings more idiomatic to the target language.
This mostly works if you have control over the underlying C-API of course, e.g. the language bindings are created by the original C-library project, not as an external project to convert a fixed C-API.
I wrote a blog post about this whole topic:
https://floooh.github.io/2020/08/23/sokol-bindgen.html
...and here's an example of one such semi-auto-generated Zig bindings, note the two "injected" helper functions at the top:
https://github.com/floooh/sokol-zig/tree/master/src/sokol
...for instance note the "injected" helper functions here:
https://github.com/floooh/sokol-zig/blob/1c93f60ad178869b84d...
-
Game Development
As you can see from the comments there are lots of options. Sokol is another one https://github.com/floooh/sokol-zig
What are some alternatives?
nodejs - Alternative StdLib for Nim for NodeJS/JavaScript targets, hijacks NodeJS StdLib for Nim
zig-bgfx-sdl2 - Minimal zig project to get bgfx running with sdl2
node-webrtc - node-webrtc is a Node.js Native Addon that provides bindings to WebRTC M87
bigger - bigg (bgfx + imgui + glfw + glm) + utils
genepi - Automatic generation of N-API wrapper from a C++ library
sokol-samples - Sample code for https://github.com/floooh/sokol
nim-webui - Use any web browser as GUI, with Nim in the backend and HTML5 in the frontend.
go - The Go programming language
gintro - High level GObject-Introspection based GTK3/GTK4 bindings for Nim language
JNA - Java Native Access
napi-rs - A framework for building compiled Node.js add-ons in Rust via Node-API
ffmpeg - FFmpeg Zig package