←back to thread

SVGs that feel like GIFs

(koaning.io)
518 points cantdutchthis | 1 comments | 08 Jul 25 08:23 UTC | HN request time: 0.229s | source
Show context
paulirish ◴[08 Jul 25 16:15 UTC] No.44501428[source]▶
If the target is a GitHub readme, then you can embed a video directly. eg https://github.com/paulirish/git-recent#readme

That said, OP's SVG trick may be a smarter choice if the content is a terminal capture.

replies(5): >>44501659 #>>44501901 #>>44503973 #>>44504356 #>>44504696 #
c-hendricks ◴[08 Jul 25 16:37 UTC] No.44501659[source]▶
If you're going this route of adding a straight up video (which isn't bad!) it helps to edit the readme directly on GitHub. That way they're uploaded to githubusercontent (or whatever the domain is) and not taking up space in your repository.
replies(1): >>44502089 #
hbn ◴[08 Jul 25 17:22 UTC] No.44502089[source]▶
Were people doing that other option?

The idea of committing a video to your repository for a PR seems silly. Every PR adds a new video to the codebase? Do you make a PR to prune them every once in a while?

replies(1): >>44503084 #
1. aziaziazi ◴[08 Jul 25 19:14 UTC] No.44503084[source]▶
> Every PR adds a new video to the codebase

Git commits only differences with the precedent commit, not the entire repository. Therefore the video is only committed once as long as that video doesn’t change.