README: start a section on the use cases for a Go obfuscator #815
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This type of question has popped up a number of times before, particularly when someone unfamiliar with obfuscators in other languages first hears about the existence of one for Go.
|
Input welcome; I'd rather answer this upfront in the README than have to come up with a new answer every time. Some people will always think that using an obfuscator is a bad idea, or even that one shouldn't exist, but that's fine. |
pagran
approved these changes
Dec 3, 2023
|
I'm not sure; it is a common question too, but the answer is still largely the same. Do you think it would have a significantly different answer? I think the text I added here already covers the reasons why an obfuscator is useful, be it for doing good or not. |
lu4p
approved these changes
Dec 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(see commit message)