Remove YAML processing library #768
Merged
Conversation
This file contains hidden or 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
We've switched from using YAML to using JavaScript directly for storing data. One reason to do that was simply that it's the only easy way to load data when running locally. A second reason, however, is that this means we can completely eliminate the use of this library at run-time. Not using a library at *all* eliminates the need to maintain it, update it, etc. It also speeds loading; nothing loads faster than code you don't load at all :-). Signed-off-by: David A. Wheeler <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
We've switched from using YAML to using JavaScript directly for storing data. One reason to do that was simply that it's the only easy way to load data when running locally.
A second reason, however, is that this means we can completely eliminate the use of this library at run-time. Not using a library at all eliminates the need to maintain it, update it, etc. It also speeds loading; nothing loads faster than code you don't load at all :-).