SDL VS zig

I don't know for sure, but could it be this?

https://github.com/libsdl-org/SDL

The kit has been fun. My daughter loved helping me wire it up to a dummy box, and we decided its worth moving forward with a desktop cabinet build. I don't have a raspberry pi and can't find one, so we're using a 2012 mac mini. OpenEmu has been fun, but I'd like to be able to control the whole UI with the joystick, so we looked at EmulationStation-DE (retropie for desktop as its been explained to me). The control kit worked with OpenEmu but not EmulationStation, and the folks over in that sub said its not supported by SDL https://github.com/libsdl-org/SDL

There is also SDL, which is a bit of a behemoth library, but gives you a lot of firepower if you want to get down to the nuts and bolts of building something from scratch with media. It provides a framework for working with graphics, sound, input hardware, etc., and is cross-platform. I haven't personally used SDL but it's a pretty well-utilized library. It's written in C so the same caveats apply as before, but works just fine with C++.

This has already been fixed in the latest SDL version, but it's likely that the game comes bundled with it's own version.

I got tired of writing C# bindings code by hand to interop with native C/C++ libraries, so I automated the process. Example for SDL: https://github.com/bottlenoselabs/SDL-cs. The repository is automated daily using Dependabot to run C2CS, generate the P/Invoke code, and push a Git commit with the code automatically when there is a change to https://github.com/libsdl-org/SDL.

The source code for it can be found at https://github.com/libsdl-org/SDL , this may be helpful if your looking for an example of how a 'platform layer' like this it can be implemented.

Simple Directmedia Layer: a library that offers low-level access to resources like audio, video graphics, joystick, keyboard, mouse. It is mainly used for the development of video games (Stepmania and Valve's games such as Counter Strike: Source, as some examples).

Now, we'll need to source the latest SDL source tarball. You can find it [here](https://github.com/libsdl-org/SDL), but you can source the latest as of this writing with the command below. Run cd, and then run:

Game library: https://github.com/libsdl-org/SDL

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

1. ZIG - $103,611

ESP32 and STM32 support is very welcome!

I have been following https://github.com/ziglang/zig/issues/5467 for a while and progress seemed to have slowed significantly

I have never used it directly, take what I say with a grain of salt.

As far as I know at least part of the idea was to eliminate the function coloring problem by letting the compiler do some nifty compile-time deductions. This had some issues (I don't know if this is still planned, it seems like the kind of thing that should not work in practice). Additionally, there were all sorts of hard technical issues with LLVM, debugging, etc.

I recommend checking the issue tracker, eg. https://github.com/ziglang/zig/issues/6025

I personally don't understand the domain well enough at all, but honestly, I feel like (if possible) Zig should try to double down on its allocator approach.

Instead of trying to use some compile-time deduction magic explicitly pass around an "async runtime/executor" struct which you explicitly have to interact with. Why not?

Yes, fundamentally. In Rust if you take a parameter of generic type T without any bounds, you cannot call anything on it except for things which are defined for all types. If you specify bounds, only things required by the bounds can be called (+ the ones for all types). Another difference is where you get an error when you try pass something which doesn't adhere to a certain trait. In Rust you will get an error at the call site, not at the place of use (except if you don't specify any bounds).

Zig is doing just fine without any trait mechanism and it simplifies the language a lot but it does come up from time to time. The usual solution is to just get type information via @typeInfo and error out if the type is something you're not expecting [0]. Not everybody is happy about it though [1] because, among other things, it makes it more difficult to discover what the required type actually is.

[0] https://github.com/ziglang/zig/blob/b3aed4e2c8b4d48b8b12f606...

[1] https://github.com/ziglang/zig/issues/17198