bgthompson

3 ms·

1.
Miegakure Siggraph 2025 Talk(youtube.com)
1 points by bgthompson 1y ago|0 comments
2.
by bgthompson 1y ago
Hot code swapping will be huge for gamedev. The idea that Zig will basically support it by default with a compiler flag is wild. Try doing that, clang.
3.
by bgthompson 1y ago
This is already such a huge achievement, yet as the devlog notes, there is plenty more to come! The idea of a compiler modifying only the parts of a binary that it needs to during compilation is simultaneously refreshing and totally wild, y
4.
by bgthompson 1y ago
Ultimately, this will be determined by the scope of the project, and depends on whether you count using an existing C library as part of the Zig ecosystem. If you want Zig libraries that don't call any C/C++ code whatsoever, then
5.
by bgthompson 1y ago
My game has a bunch of strings, and my string code currently looks very different to this! For example, copying two lines from source: var buffer : [64] u8 = undefined; const level_name_cstring : stringnt = std.fmt.bufPrintZ(&buff
6.
by bgthompson 1y ago
For my (relatively simple) use cases, I've had a significantly better time using comptime than templates; the syntax and the quality of the error messages are a lot simpler in Zig. While I've never attempted to do anything super f
7.
by bgthompson 1y ago
You're welcome! My experience with the breaking changes in Zig has not been bad at all. For brevity in the blog I didn't get into what I had to do to get things working again, but the process itself was straightforwards. Sometimes
8.
Reflecting on a Year of Gamedev in Zig(bgthompson.codeberg.page)
118 points by bgthompson 1y ago|121 comments