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

Deduplicate "Brainfuck generator" kata #84

Closed
1 task done
hobovsky opened this issue Feb 14, 2022 · 9 comments
Closed
1 task done

Deduplicate "Brainfuck generator" kata #84

hobovsky opened this issue Feb 14, 2022 · 9 comments
Assignees
Labels
discussion/deduplicate Discussion and vote what to do with duplicate kata

Comments

@hobovsky
Copy link
Contributor

hobovsky commented Feb 14, 2022

  1. Brainfuck generator
  • Published Jul 2016, author active.
  • No pending issues.
  • Pending Rust translation.
  1. Generate BF Program from Target Output
  • Published Dec 2016, author active.
  • One pending issue.
  • Pending Java translation.

Both kata are very similar: ranked as 6 kyu, and have similar satisfaction (~95%) and completion rate (~100+ solutions). They accept the same type of solutions (the most trivial programs, not optimized for length of code).
Both kata have the same amount of translations and languages, and no overlap between them. Whichever kata gets selected to stay, the other one will have to be merged into it.


Conclusion:

@hobovsky hobovsky added the discussion/deduplicate Discussion and vote what to do with duplicate kata label Feb 14, 2022
@hobovsky
Copy link
Contributor Author

Since both kata are very similar, I vote to keep the older one (i.e. 1.).
As both authors are active, I'd hope they'd help with migration of translations ;)

@wtlgo
Copy link

wtlgo commented Feb 14, 2022

I also think we should merge the second one into the first one, and keep the first.

@Blind4Basics
Copy link

Authors should almost discuss between them to get an agrement. If they cannot, then the community could step up and take over the decision?

@ejini6969
Copy link

I haven't solved any of them, but I do not have any preference whatsoever.

@Kacarott
Copy link

I agree with keeping 1. In the case where two katas are of about equivalent quality, the older one should always be prioritised.

@2bitsin
Copy link

2bitsin commented Feb 14, 2022

Author of first one here
I'm fine with whatever action you take.

@monadius
Copy link

The second kata has an incorrect BF interpreter (at least in JS): the command . does not output 0.

@monadius
Copy link

I vote to keep 1 and retire 2. It will be easy to move 2 languages; moreover, this kata deserves more translations.

@hobovsky
Copy link
Contributor Author

Since both authors explicitly stated they will be fine with any decision, I think it's OK to conclude early.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion/deduplicate Discussion and vote what to do with duplicate kata
Projects
Development

No branches or pull requests

8 participants