Deliver a fatal blow to YAML #4
Merged
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
YAML's biggest flaw is that it simply isn't a safe file format. A YAML file can be truncated virtually arbitrarily ... and remain a valid YAML file. This causes semantic corruption and missing elements in scenarios as routine as a partial file transfer, a nearly full filesystem, or an editor crash. JSON, XML, everything short of dumb .ini files, has terminators and so avoids this problem.
|
Thank-you! |
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.
YAML's biggest flaw is that it simply isn't a safe file format. A YAML file can be truncated virtually arbitrarily ... and remain a valid YAML file. This causes semantic corruption and missing elements in scenarios as routine as a partial file transfer, a nearly full filesystem, or an editor crash. JSON, XML, everything short of dumb .ini files, has terminators and so avoids this problem.