SemanticDiff
age
SemanticDiff | age | |
---|---|---|
13 | 214 | |
39 | 15,490 | |
- | - | |
3.2 | 4.9 | |
30 days ago | about 1 month ago | |
Go | ||
- | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SemanticDiff
-
Difftastic, a structural diff tool that understands syntax
Semantic Diff is probably the closest for now, although I don't think it uses tree-sitter.
https://semanticdiff.com/
Found via https://github.com/Wilfred/difftastic/issues/194.
-
My programming language aware diff for VS Code and GitHub now supports Rust
I am working on SemanticDiff, a programming language aware diff that hides style-only changes, detects moved code and refactorings. I just added support for Rust and would like to know what you think!
-
Prettier $20k Bounty was Claimed
If you're looking for a VS Code extension or a GitHub app, check out https://semanticdiff.com/. I'm a co-founder of this project.
If you prefer a CLI tool, check out https://github.com/Wilfred/difftastic. It supports more languages, but doesn't recognize when code has been replaced by an equivalent version ("invariances"). So it will show some changes (e.g. replacing a character in a string with an escape sequence) even though they are technically equivalent.
-
Large pull requests slow down development
There are some tools that can separate actual code changes from reformatting changes. I am working on https://semanticdiff.com, a VS Code Extension / GitHub App that can help you with this. There is also difftastic if you prefer a CLI based solution. It supports more languages but can detect fewer types of reformatting changes.
-
Pijul: Version-Control Post-Git ā¢ Goto 2023
I'm not familiar with Pijul, and haven't finished watching this presentation, but IME the problems with modern version control tools is that they still rely on comparing lines of plain text, something we've been doing for decades. Merge conflicts are an issue because our tools are agnostic about the actual content they're tracking.
Instead, the tools should be smarter and work on the level of functions, classes, packages, sentences, paragraphs, or whatever primitive makes sense for the project and file that is being changed. In the case of code bases, they need to be aware of the language and the AST of the program. For binary files, they need to be aware of the file format and its binary structure. This would allow them to show actually meaningful diffs, and minimize the chances of conflicts, and of producing a corrupt file after an automatic merge.
There has been some research in this area, and there are a few semantic diffing tools[1,2,3], but I'm not aware of this being widely used in any VCS.
Nowadays, with all the machine learning advances, the ideal VCS should also use ML to understand the change at a deeper level, and maybe even suggest improvements. If AI can write code for me, it could surely understand what I'm trying to do, and help me so that version control is entirely hands-free, instead of having to fight with it, and be constantly aware of it, as I have to do now.
I just finished watching the presentation, and Pijul seems like an iterative improvement over Git. Nothing jumped out at me like a killer feature that would make me want to give it a try. It might be because the author focuses too much on technical details, instead of taking a step back and rethinking what a modern VCS tool should look like today.
[1]: https://semanticdiff.com/
[2]: https://github.com/trailofbits/graphtage
[3]: https://github.com/GumTreeDiff/gumtree
-
I added Go support to my VS Code extension for programming language aware diffs
You mean copying chunks from one file/side to the other? If that is the case, you might want to subscribe to this issue that was opened a few days ago. Since the extension does not work on a line-by-line level, it is a bit more difficult than for normal diffs. For example, what should happen if the formatting differs between both files. Should SemanticDiff copy it over as well or try to merge the changes? I will try to post an update on/in this issue soon and maybe have a discussion about the expected behavior.
- SemanticDiff ā Language Aware Diff for VS Code
-
My Visual Studio Code extension for programming language aware diffs is now in public beta!
Feel free to open an issue at https://github.com/Sysmagine/SemanticDiff/issues so that we can keep you updated on the progress.
-
Searching for beta testers for my VS Code extension that makes diffs more readable
Feel free to open feature requests for any languages you need: https://github.com/Sysmagine/SemanticDiff/issues
age
-
keepsecret.py: a simple way to encrypt secret files in your repository
age
- Age: A simple, modern and secure encryption tool
-
Joining ChatCraft.org
and echoing the result after converting to an age private key
-
What is the point of a public key fingerprint?
I like that https://github.com/FiloSottile/age has small public keys.
-
OpenPGP Forked into "LibrePGP" by GnuPG's Maintainer Werner Koch
> something fresh
It exists, it's called age..
Some random links
https://github.com/FiloSottile/age
https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...
https://github.com/FiloSottile/age/discussions/432
> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..
Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Prettier $20k Bounty was Claimed
I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:
https://github.com/FiloSottile/age/discussions/432
https://words.filippo.io/dispatches/age-authentication/
-
Cosmopolitan Third Edition
of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...
-
Would you trust a repository made like this to save your secrets?
Why keep something secret on a public repo? Is that not an oxymoron?
Also, Iām terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.
[0] https://github.com/FiloSottile/age
-
Looking For Encryption App
Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.
What are some alternatives?
mergify - Merge git changes on commit at a time.
sops - Simple and flexible tool for managing secrets
git-machete - Probably the sharpest git repository organizer & rebase/merge workflow automation tool you've ever seen
Picocrypt - A very small, very simple, yet very secure encryption tool.
vscode-settings - My VS Code settings and extensions
rage - A simple, secure and modern file encryption tool (and Rust library) with small explicit keys, no config options, and UNIX-style composability.
graphtage - A semantic diff utility and library for tree-like files such as JSON, JSON5, XML, HTML, YAML, and CSV.
age-plugin-yubikey - YubiKey plugin for age
difftastic - a structural diff that understands syntax š„š©
minisign - A dead simple tool to sign files and verify digital signatures.
git-stack - Stacked branch management for Git
OpenKeychain - OpenKeychain is an OpenPGP implementation for Android.