Open
Conversation
Add a before/after animation showing native fetch verbosity vs ofetch's clean one-liner API. Generated with Remotion. Co-authored-by: Cursor <cursoragent@cursor.com>
bc00e6a to
32cba7e
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
fetchvs ofetch's clean one-liner APIassets/demo.gif(~1.1 MB)The animation was generated with Remotion using the Catppuccin Mocha color scheme.
Preview
The GIF shows:
Motivation
ofetch's README is thorough but entirely text-based. A visual before/after at the top immediately communicates why someone would choose ofetch over native fetch.
Made with Cursor