TrinityCore VS zig

You could take a look at TrinityCore[1] and adjacent projects! Best of luck!

[1] https://github.com/TrinityCore/TrinityCore

TrinityCore: https://www.trinitycore.org/ send email for your questions, or look at this video if you want https://www.youtube.com/watch?v=tAJ0dvNuARs

Trinitycore has 3.4.0 for Wotlk classic but it's pure sandbox. It's so much work to be done so don't expect it to be released. https://github.com/TrinityCore/TrinityCore/tree/wotlk_classic

You can host your own WoW server locally! I would personally recommend TrinityCore. It can be a little bit of a hassle, here's a setup guide.

If they use the base TrinityCore code there's no processing (the whole point of GetAll is a minimal processing dump of the data as-is). You can see the commit for it here https://github.com/TrinityCore/TrinityCore/commit/3aaeb574050668e5a240078f6e40337c3975d110 and you can see it just dumps what is there until 55k then stops hard.

You can just compile one here - https://github.com/TrinityCore/TrinityCore

TrinityCore, AzerothCore- C++, these and others like them are the server for projects- well-known for being used on private WOW servers, so they're probably good enough for your personal project https://www.libhunt.com/r/TrinityCore - https://www.trinitycore.org/ - https://www.azerothcore.org/

There is an issue proposing this approach: https://github.com/ziglang/zig/issues/4284

https://github.com/ziglang/zig/issues/224

e.g.:

> > When debugging/prototyping, it's useful to comment out a line without having to refactor, e.g.

When writing code in a scripting language, sometimes you need that extra bit of performance (or maybe an async feature from Zig).

NodeJS is by no means a slow runtime, it wouldn’t be so popular if it was. But compared to Bun, it’s slow. Bun was built from the ground up with speed in mind, using both JavascriptCore and Zig. The Bun team spent an enormous amount of time and energy trying to make Bun fast, including lots of profiling, benchmarking, and optimizations.

ntdll.dll!RtlUserThreadStart()

There are valid reasons to use APIs from NTDLL. Where I disagree with zig#1840 is the idea that it is always better to use NTDLL versions of API. Every other software ecosystem uses the standard Win32 APIs and diverging from that without a good reason seems like a good way to have unexpected behavior. One concrete example is most users and programmers expect Windows to redirect some file system paths when running on WOW64. But this is implemented in Kernel32, not ntdll.

https://github.com/ziglang/zig/issues/11894

Zig also has an IRC channel on libera (#zig) that is moderated by Andrew Kelley.[1]

[1] https://github.com/ziglang/zig/wiki/Community