awesome-structure-editors
graphtage
awesome-structure-editors | graphtage | |
---|---|---|
10 | 12 | |
305 | 2,330 | |
- | 0.8% | |
4.2 | 8.1 | |
20 days ago | 14 days ago | |
Python | Python | |
Creative Commons Zero v1.0 Universal | GNU Lesser General Public License v3.0 only |
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.
awesome-structure-editors
-
Ask HN: Can we do better than Git for version control?
Yes, I think that we can do better than plain text as the source of truth, and thus git would probably need to change.
There's work around a bunch of languages that are not based on text, some have their own editor or a tool to manage a canonical representation in text for you that would make them friendlier to git.
- https://github.com/yairchu/awesome-structure-editors/blob/main/README.md
- Structure Editors: A list of projectional code editor projects
-
Pijul: Version-Control Post-Git • Goto 2023
There's many more akin projects listed in https://github.com/yairchu/awesome-structure-editors/blob/ma...
I can't wait fast enough for these ideas to reshape how we deal with programs and build stuff.
-
Is Haskell gaining or losing popularity?
Haskell seems to be pretty big. For example in this list of projects it appears to be the second most popular language (after TypeScript) :)
-
Ask HN: Any IDEs or text editor plugins with AST-driven navigation?
See https://github.com/yairchu/awesome-structure-editors
-
A Block-Based Functional Programming Language
You could submit a pull request to get it added to awesome-structure-editors by /u/yairchu
-
Emacs Is Not Enough
It would be interesting to have such a general project go somewhere.
While in principle structural editing sounds like an incredible advance, there are 'good enough' advantages to plain-text tools that make it a much more practical solution. The other issue is of course integration with existing tooling, which you either skip entirely or compromise on the design.
What I feel is missing, between the description of "old, bad state of things" and "utopian vision" is a review of some of the projects that already tried to achieve this ideal state. It turns out there are a number of them, and most of them failed to achieve any traction or impact [0].
The rants are very long, so I skimmed quickly the one about git; I understand the complaints, although git is only bringing me joy and no pain --interactive rebase, absorb and a few aliases made it a breeze. But in a similar fashion there are projects trying to solve its fundamental issues, like pijul(.org); what are they missing?
[0] https://github.com/yairchu/awesome-structure-editors/blob/ma...
- Ask HN: Is Vim still worth learning?
- Structure Editors
-
Ask HN: More “experimental“ UIs for editing/writing code?
Some good ones pops up in Projectional Programming [1] once in a while. The pinned thread links to the structure-editors github list [2] too.
[1] https://www.reddit.com/r/nosyntax/
[2] https://github.com/yairchu/awesome-structure-editors
graphtage
-
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
- graphtage - A semantic diff utility and library for tree-like files such as JSON, JSON5, XML, HTML, YAML, and CSV.
-
comparing two jsons element-wise
Vielleicht mal https://github.com/trailofbits/graphtage abchecken
-
Hacker News top posts: Feb 27, 2021
Graphtage: A semantic diff utility for JSON, HTML, YAML, CSV, etc\ (42 comments)
- Graphtage: A semantic diff utility for JSON, HTML, YAML, CSV, etc
What are some alternatives?
lisperanto - Lisperanto is a spatial canvas for programming; Lisperanto is a spatial canvas for knowledge; Lisperanto is a spatial canvas for ideas;
bit - Bit is a modern Git CLI
unit - Next Generation Visual Programming System
visual-dom-diff - Highlight differences between two DOM trees.
metadesk
webdiff - Two-column web-based git difftool
git-stack - Stacked branch management for Git
gqlalchemy - GQLAlchemy is a library developed with the purpose of assisting in writing and running queries on Memgraph. GQLAlchemy supports high-level connection to Memgraph as well as modular query builder.
gtoolkit - Glamorous Toolkit is the Moldable Development environment. It empowers you to make systems explainable through experiences tailored for each problem.
GJSON - Get JSON values quickly - JSON parser for Go
git-machete - Probably the sharpest git repository organizer & rebase/merge workflow automation tool you've ever seen
communities - Library of community detection algorithms and visualization tools