Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change naming #383

Open
avivace opened this issue Jun 18, 2022 · 2 comments
Open

Change naming #383

avivace opened this issue Jun 18, 2022 · 2 comments

Comments

@avivace
Copy link

avivace commented Jun 18, 2022

I have the feeling that the current name is quite confusing and counter intuitive. It kind of implies that this version is from 2020.

Is the old one still relevant at all? Why not simply call it GBDK now? (with a major version bump from the old one?) or GBDK-x (with x being whatever but not a temporal reference?)

@bbbbbr
Copy link
Collaborator

bbbbbr commented Jun 19, 2022

I'm going to make this lengthier so it might serve as an FAQ :)

We get asked about the name periodically, but have no plans to change it at this time.

People do joke on occasion about it no longer being 2020, but in practice we haven't yet seen confusion related to versioning. The actual release packages have distinct version numbers (for example, currently 4.0.6).

Some additional context:

  • 2020 was the Resurrection date for GBDK, when it's new maintenance era began
  • GBDK-2020 is the project name based on the above, and is not a version (The first GBDK-2020 version was 3.0, picking up after GBDK's 2.96)
  • GBDK as a bare name is not always available on services, whereas "GBDK-2020" almost always is
  • Having a distinct name from the original GBDK helps to differentiate descriptively and for search. For example, instead of having to try and describe the project differences as "old" vs "new" GBDK with some ambiguity, it's easy to say "GBDK-2020" and it is clear which project and code base is intended.
  • 2020 can also mean "20/20", as in clarity :D

Similarly GBDK-2020 is now more than just a Game Boy Dev Kit, it can also be used for several other platforms (SMS/GG/etc). So sometimes we also think of it more generally as "Game Builder Dev Kit".

@bbbbbr bbbbbr pinned this issue Jun 19, 2022
@bbbbbr bbbbbr closed this as completed Jun 19, 2022
@bbbbbr bbbbbr reopened this Jun 19, 2022
@bbbbbr
Copy link
Collaborator

bbbbbr commented Jun 19, 2022

I guess I can't pin with it closed, reopening for now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants