syntactic_versioning VS locust

Compare syntactic_versioning vs locust and see what are their differences.

syntactic_versioning

What if Git worked with Programming Languages? (by GavinMendelGleason)

locust

"git diff" over abstract syntax trees (by bugout-dev)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
syntactic_versioning locust
8 4
98 47
- -
0.0 0.0
over 2 years ago 5 months ago
Python
- MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

syntactic_versioning

Posts with mentions or reviews of syntactic_versioning. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-28.

locust

Posts with mentions or reviews of locust. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-10-06.
  • Effective Code Browsing
    7 projects | news.ycombinator.com | 6 Oct 2021
    Nice!

    Have been working on something similar, although my use case is more about learning how code has changed across git commits: https://github.com/bugout-dev/locust

    For Javascript/Typescript/React support, like you, I hooked into the Babel toolchain. Can't recommend it highly enough.

    There's also a newish project called quick-lint-js which seems to have written their own from-scratch AST parser for JS, but I haven't tried it yet: https://github.com/quick-lint/quick-lint-js

    Finally, another project that I know in this space is comby (I believe it is owned/maintained by the folks at Sourcegraph): https://comby.dev/

    Don't know why I dumped all those links there. Just figured there may be something useful in them for you. Am also just super passionate about building knowledge about code bases by analyzing their ASTs. Nice to meet a fellow enthusiast. :)

  • What if Git worked with Programming Languages?
    17 projects | news.ycombinator.com | 27 Sep 2021
    I maintain a free/open source project that does exactly what the author asks for: https://github.com/bugout-dev/locust.

    Our tool uses git as the foundation of its functionality. It superimposes git diffs on top of ASTs.

    It is insanely powerful.

    For example, we use it to power semantic code search and current support Python, Javascript, and Java. We generate a JSON object defining the AST differences between initial and terminal commits on GitHub PRs and doing text search on the JSON objects performs surprisingly well when we want to answer questions like, "When did we add dateutils as a dependency?" or "When did we last change the /journals handler on the API?"

    The Python integration currently sees the most use but if you are interested in other languages, we would be happy to support it.

    Do drop me a DM if you want help getting started with Locust.

  • Diffsitter: A tree-sitter based AST difftool to get meaningful semantic diffs
    8 projects | news.ycombinator.com | 18 Jul 2021
    My team has a similar project (Locust: https://github.com/bugout-dev/locust) where the goal is to learn the semantic meanings of code changes in git commits, GitHub PRs, etc.

    Since we took git diffs as a target for semantic analysis, we have a different approach to our diffs. We start with line-by-line diffs (specifically using "git diff") and then take a semantic diff by superimposing the git diff information on top of the initial and terminal ASTs.

    This makes the diff calculation cheaper because we don't have to do full diff between trees.

    Haven't updated the code in a few months, but my team is actively using Locust on public GitHub repos to learn the semantics of those code bases. We do plan to do some work on it soon to make it easier to make Locust easier to use (especially as a library).

    Really need to sit down and take a proper look at tree-sitter. We currently support Locust diffs for Python, Javascript, and Java, but each one is custom written and implements the same basic algorithm. It looks like tree sitter might just crush this problem for us.

  • Difftastic: Syntax-aware structured diff tool
    6 projects | news.ycombinator.com | 7 Jul 2021

What are some alternatives?

When comparing syntactic_versioning and locust you can also consider the following projects:

weggli - weggli is a fast and robust semantic search tool for C and C++ codebases. It is designed to help security researchers identify interesting functionality in large codebases.

gumtree - An awesome code differencing tool

difftastic - a structural diff that understands syntax 🟥🟩

nvim-treesitter-context - Show code context

TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

nbdime - Tools for diffing and merging of Jupyter notebooks.

diffsitter - A tree-sitter based AST difftool to get meaningful semantic diffs

diffr - Yet another diff highlighting tool

delta - A syntax-highlighting pager for git, diff, and grep output

unison - A friendly programming language from the future

fzf - :cherry_blossom: A command-line fuzzy finder