TALA
Moose
| TALA | Moose | |
|---|---|---|
| 3 | 2 | |
| 177 | 133 | |
| 2.8% | 0.0% | |
| 5.0 | 7.7 | |
| 14 days ago | 18 days ago | |
| Shell | Smalltalk | |
| GNU General Public License v3.0 or later | MIT 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.
TALA
- D2 Playground
-
Architecture diagrams should be code
This is a problem with the languages, not a fundamental flaw. Manipulating text has a much higher ceiling than drag and drop, in terms of speed and simplicity. Every programmer has their own ecosystem for manipulating text. I can grep, version control, diff, jump with Vim key bindings, etc.
The layout engines are very hard. We've been making https://terrastruct.com/tala for over 2 years now. At first it seemed dubious whether it was even possible to beat Graphviz, but we've been designing it to emulate how diagrams might look on a whiteboard drawn by humans. That's a very different heuristic than the theoretical hierarchical cross-minimizations that previous algorithms strive for, and it's yielded good results for a subset of diagrams.
-
D2 language, open source alternative to PlantUML
https://github.com/terrastruct/TALA
(apologies for this path. trying to strike the balance of making it findable for those who search for it while hidden to those who just want free.)
Moose
-
Architecture diagrams should be code
I use TLA+. Almost every system has some sort of safety property that needs to be guaranteed (bad things must never happen). A good many have liveness properties (something must eventually happen). Diagrams are well and good for documentation but tell you nothing about the specifications of the system.
I tried UML once but found it lacking.
When I’m writing documentation I like to use diagrams. Mermaid has served me well. It’s integrated into GitHub these days which is convenient. I’ve also used ditaa and graphviz to good effect. With org-mode and org-babel it’s quite easy to build executable documentation: take the query from a database to build a rough ER diagram with graphviz, a shell command on a jump box to get the data-plane hosts to build into a network diagram, etc.
Another interesting tool: https://github.com/moosetechnology/Moose I haven’t spent that much time with it but I learned enough to generate a dependency graph for a NodeJS project that was useful for planning refactoring work.
-
Tree-sitter: an incremental parsing system for programming tools
Could you compare Sourcegraph to something like Moose, FAMIX, GToolkit?
https://github.com/moosetechnology/Moose
What are some alternatives?
d2 - D2 is a modern diagram scripting language that turns text to diagrams.
gtoolkit - Glamorous Toolkit is the Moldable Development environment. It empowers you to make systems explainable through experiences tailored for each problem.
d2-docs - Language documentation and blog for D2.
tree-sitter-go - Go grammar for tree-sitter
keenwrite-themes - Document typesetting configurations using ConTeXt
tree-sitter-c - C grammar for tree-sitter
flowchart-fun - Easily generate flowcharts and diagrams from text ⿻
csharp-mode - A major-mode for editing C# in emacs
text-to-diagram-site - Compare syntax, layouts, outputs between languages for generating diagrams with text.
PHP Parser - A PHP parser written in PHP
excalidraw - Virtual whiteboard for sketching hand-drawn like diagrams
tree-sitter-kotlin - Kotlin grammar for Tree-sitter