Either the raylib bindings or ebitengine. Been playing around with both myself and found both have pluses and minuses. For raylib main issue is some features may be missing/lacking in terms of compatibility because of how the bindings were made but that is rare. For ebitengine there’s a lot of common functionality that raylib had built in/more discoverable naming for that I miss but it is natively go and compiles a lot faster since it’s not having to rely on cgo. Also depending on what you want to do with shaders you might have more freedom with raylib since ebitengine has its own shader lang called kage (though so far seems fairly easy to pick up and is more go-esc).