Game Development in Go
j15r.com
Game Development in Go
1–10 of 60 posts
Re: Game Development in Go
#2"Over Quota
This application is temporarily over its serving quota. Please try again later."
Lol, last time i have seen such a message was ten years ago ;-)
Re: Game Development in Go
#3"Over Quota This application is temporarily over its serving quota. Please try again later." Lol, last time i have seen such a message was ten years ago ;-)
Damn, that was fast. Thought billing was enabled for that site, but I guess not. Fixed!
Edit: Or at least it should be. Might take a couple of minutes to clear up.
Re: Game Development in Go
#4Currently the site is unreachable (for me at least). But here I've got a Coral Cache version of the content: http://www.j15r.com.nyud.net/blog/2015/01/25/Game_Developmen...
Re: Game Development in Go
#5I already asked here before but what is the status of the GC regarding real-time games? ( for a gameserver )
Re: Game Development in Go
#6I was experimenting with the idea of learning game dev with golang but shortly after starting I realized that there's very little tooling for that and I'll probably drop that project midway. Needing to make my own engine/tools/bindings on every step drained all the enthusiasm.
Would love to see something like LÖVE made available for golang
Re: Game Development in Go
#7I already asked here before but what is the status of the GC regarding real-time games? ( for a gameserver )
Minecraft seems to be doing okay. The key is to have many small GC pauses instead of few big pauses.
Re: Game Development in Go
#8Did you at all find that the printf methodology of debugging got in the way of the gamedev? I've been keeping an eye on Go, but have been hesitant to approach it seriously because of that debugging approach.
Re: Game Development in Go
#9Did you at all find that the printf methodology of debugging got in the way of the gamedev? I've been keeping an eye on Go, but have been hesitant to approach it seriously because of that debugging approach.
I have worked with GDB and Go before; it's not intractable, just more difficult to interpret.
Printf frequently works very well for most debugging, especially server side. I use the regular logging module pointed at stdout instead of printf specifically, and increasing the debugging level works most of the time.
Its also nice that with a bit of metaprogramming and goroutines/channels, you can make log printing nearly free. I once saw a technique where you simply write your really detailed log messages to a ring buffer (using a lockfree algorithm), and spit them out when you fail. This is even easier to do in Go, since you can just send the messages over a channel and not have to worry about properly implementing a lock free algorithm, and spit them out in a `recover()` function surrounding your main (or look at them in GDB).
Re: Game Development in Go
#10I was experimenting with the idea of learning game dev with golang but shortly after starting I realized that there's very little tooling for that and I'll probably drop that project midway. Needing to make my own engine/tools/bindings on every step drained all the enthusiasm. Would love to see something like LÖVE made available for golang
[deleted]