|
|
|
|
|
by hu3
2017 days ago
|
|
I've toyed with Ebiten. It's wonderful. Here are some pain points: - I've had trouble with sub-texture bleeding requiring me to add paddings between my texture atlas. This could probably also be resolved by not having my own texture atlas and loading each texture separatedly but I like my atlas. - If you like class inheritance to compose hierarchy of objects, Go isn't well suited. This can be good or bad depending on how you like to architecture. What I love about Ebiten and Go is the fast compilation times which makes the edit-compile-run feedback loop short and sweet. The author is friendly, accessible and responsive on slack. Join here https://invite.slack.golangbridge.org/ then head to #ebiten here https://gophers.slack.com/app_redirect?channel=ebiten |
|