Go-SDL icon indicating copy to clipboard operation
Go-SDL copied to clipboard

which fork should i use?

Open michikaze opened this issue 11 years ago • 1 comments

this repository seems to be unactive for two years, and there are 74 forks, but i don't know which to choose. Which is best?

michikaze avatar Aug 22 '13 19:08 michikaze

Hi there,

I've been looking for an answer to this myself. The answer for me was to create my own fork and cherry-pick good changes (read: bugfixes, doc updates, features, etc) into my repository. This isn't a one-size-fits-all solution -- if you're not familiar with git, it could be a bit panic-inducing -- but I think this repo is at least a good starting point.

The things that I aim to fix in my fork:

  • Outdated documentation (a lot of this stuff seems to be pre-go-1.0, yikes)
  • No Mac or Windows support
  • Bindings are on SDL 1.2 - with the recent release of SDL 2.0, it would be nice to update from 1.2

A lot of these things are sitting in pull requests or just in other forks! Obviously it needs to be tested and not blindly accepted, but there's a lot of potential.

I'm still sifting through the various forks, so I don't have any updates yet, but hopefully I'll have some improvements in my own repository soon.

EDIT: due to the tremendous amount of changes between SDL 1.2 and 2.0, I've decided to start from scratch. Contributions welcome!

adam000 avatar Jan 02 '14 03:01 adam000