jtree VS Gource

The `grammar` files are written in a Tree Language called Grammar. Those are your schema files. You basically create a new syntax-free plain text "language" for storing your data, in this case 1 "car" file per model of car.

It was a pipedream of mine until the M1's came out. Those changed everything, because then it became fast enough to actually do it.

We have a new release coming out soon with a new query language that will change everything. Here is the source code: https://github.com/breck7/jtree/tree/main/treeBase

Don't have time to install but I would pay $10 in NEAR coin if you can email or post the results of my repos to me ([email protected]):

https://github.com/breck7/jtree and https://github.com/breck7/pldb

I mean I've tried (https://github.com/breck7/jtree/issues/31). TypeScript is pretty solid.

You should see the 3 symbols as configurable in all implementations (for example, https://github.com/treenotation/jtree/blob/8ac7f4c66a76775f84f02c8ee533eaa8054bff31/core/TreeNode.ts#L1497 can be changed via a method overload).

The underlying technology, https://gource.io/, has probably been mentioned here before, but it's a superb tool which produces beautiful animations, so deserves another airing.

This is really cool. And as OP pointed out, I really like the pipeline integration. Like when linting catches function-level complexity, but in a cross functional way. I prefer to think of programs in layers where the top layers can import lower layers, but never the other way (and also very cautious on horizontal imports). Something like this would help track that.

From the visualization perspective, it reminds me a lot of Gource. Gource is a cool visualization showing contributions to a repo. You see individual contributors buzzing around updating files on per-commit and per-merge.

https://github.com/acaudwell/Gource

Nešto kao gource?

Yeah, I was completely distracted trying to figure out what `import { Button, icons } from "ui"` was derived from. Looks like `

That being said, I do like the overall idea of animating code changes. Calls back to that old Facebook sketching app[0] that would let us share replays, and I am a fan of the stories that Gource[1] can tell.

Ultimately, though, the sequential text file is a bad metaphor for code. Best thing for it is to split your modules across files.

0. Can't remember the name of it, but something similar is https://sketchtoy.com/

1. https://gource.io/

If the goal is to create a fun animation, then have a look at https://gource.io/ for inspiration.

From https://github.com/acaudwell/Gource

I wonder what your history would look like in Gource: https://gource.io/