Azul3D – A 3D game engine written in Go
azul3d.org
Azul3D – A 3D game engine written in Go
1–10 of 46 posts
Re: Azul3D – A 3D game engine written in Go
#2What's with the package versioning?
http://azul3d.org/doc/versioning.html#development-versions
v1 (latest version)
import "azul3d.org/audio.v1"
v0 (in development)
import "azul3d.org/audio.v0"
Is this normal for go packages?
Re: Azul3D – A 3D game engine written in Go
#3Garbage collector FAQ isn't necessarily reassuring, since it seems to say "go through the same hoops other GC gaming platforms push you through". Obligatory Rust gaming comment goes here.
Re: Azul3D – A 3D game engine written in Go
#4Good job~ And the next version's Go will support developing games on android
Re: Azul3D – A 3D game engine written in Go
#5What's with the package versioning? http://azul3d.org/doc/versioning.html#development-versions v1 (latest version) import "azul3d.org/audio.v1" v0 (in development) import "azul3d.org/audio.v0" Is this normal for go packages?
It's not normal, but package versioning in go is broken, so people invent their own workarounds
Re: Azul3D – A 3D game engine written in Go
#6What's with the package versioning? http://azul3d.org/doc/versioning.html#development-versions v1 (latest version) import "azul3d.org/audio.v1" v0 (in development) import "azul3d.org/audio.v0" Is this normal for go packages?
That's one way of doing it. Another is to just use their github path and use vendoring tools like godep.
I prefer vendoring since it doesn't rely on a 3rd party being online or existing in a year. Also it's simpler when you want to have repeatable builds, since the vendored code is usually in your repo. It's also convenient for CI/CD things, since your repo ships as a unique component.
Also using versioned path like that means that a version bump means editing all your files. Across a large project, it becomes harder to manage.
However, versioned path aren't incompatible with vendoring tools. So one doesn't prevent the other.
FWIW, I think versioned path is also not very popular in the pseudo-contest of vendoring code/versioning path.
Re: Azul3D – A 3D game engine written in Go
#7Garbage collector FAQ isn't necessarily reassuring, since it seems to say "go through the same hoops other GC gaming platforms push you through". Obligatory Rust gaming comment goes here.
I never read it like that at all.
To me it says be mindful when allocating memory. This is no more effort than having to manually allocate and free memory, but also has the convenience and safety of a GC to fall back on.
Re: Azul3D – A 3D game engine written in Go
#8go get azul3d.org/examples.v1/... is enough, you don't need go get azul3d.org/examples.v1
Re: Azul3D – A 3D game engine written in Go
#9No screenshots of the game at all?
Re: Azul3D – A 3D game engine written in Go
#10"No, and it likely never will. Azul3D is for programmers and doesn't provide GUI-editors."
So, you write your levels using a text editor? That's not for programmers, that's for people who hate themselves.