[GH-ISSUE #1] Suggestion to rename YesN't Interpreter to Red Interpreter #1

Closed
opened 2026-09-04 00:51:00 +02:00 by Stone_Red · 1 comment
Owner

Originally created by @alibutt30 on GitHub (Oct 2, 2024).
Original GitHub issue: https://github.com/Stone-Red-Code/YesNt-Interpreter/issues/1

The current name of the YesN't interpreter is not only hard to pronounce, it lacks the catchiness too.

The suggestion is to therefore rename it to a more catchy word like Red interpreter.

Originally created by @alibutt30 on GitHub (Oct 2, 2024). Original GitHub issue: https://github.com/Stone-Red-Code/YesNt-Interpreter/issues/1 The current name of the YesN't interpreter is not only hard to pronounce, it lacks the catchiness too. The suggestion is to therefore rename it to a more catchy word like Red interpreter.
Author
Owner

@Stone-Red-Code commented on GitHub (Oct 2, 2024):

Closed because of the like/dislike ratio.
Seems like the community doesn't like this name.

<!-- gh-comment-id:2388424809 --> @Stone-Red-Code commented on GitHub (Oct 2, 2024): Closed because of the like/dislike ratio. Seems like the community doesn't like this name.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Stone_Red/YesNt-Interpreter#1