Go Games: Difference between revisions
Jump to navigation
Jump to search
Adamcolton (talk | contribs) No edit summary |
Adamcolton (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
* https://github.com/azul3d/engine : Looks good for 3d games. | * https://github.com/azul3d/engine : Looks good for 3d games. | ||
* https://github.com/hajimehoshi/ebiten : 2D web browser games | * https://github.com/hajimehoshi/ebiten : 2D web browser games | ||
== DIY == | |||
Because of course. Then again, I've got my vec2d package that's pretty good and the stuff I built in Javascirpt I liked, redoing that in Go won't require a lot. I like a lot of what Oakmound did, I just don't like how they did it, so I can use a lot of their code. For screen management, use their shiny fork: | |||
https://github.com/oakmound/shiny | |||
Revision as of 14:47, 3 July 2018
Engines
- https://github.com/oakmound/oak : I like this, looks simple but solid. I like their "no-deps" goal.
- https://github.com/g3n/engine : Not sure about the dependencies (requires gcc)
- https://github.com/azul3d/engine : Looks good for 3d games.
- https://github.com/hajimehoshi/ebiten : 2D web browser games
DIY
Because of course. Then again, I've got my vec2d package that's pretty good and the stuff I built in Javascirpt I liked, redoing that in Go won't require a lot. I like a lot of what Oakmound did, I just don't like how they did it, so I can use a lot of their code. For screen management, use their shiny fork: