csharp-mode
Moose
| csharp-mode | Moose | |
|---|---|---|
| 4 | 2 | |
| 153 | 133 | |
| 0.0% | 0.0% | |
| 0.0 | 7.7 | |
| over 1 year ago | 16 days ago | |
| Emacs Lisp | Smalltalk | |
| GNU General Public License v3.0 only | 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.
csharp-mode
-
Error trying to load csharp mode -- weird interaction with R-mode???
csharp-mode is an installed package. Status: Installed in ‘csharp-mode-20210105.1950/’ (unsigned). Delete Version: 20210105.1950 Summary: C# mode derived mode Homepage: https://github.com/emacs-csharp/csharp-mode Keywords: c# languages oop mode Other versions: 0.11.0 (installed), 20211124.1105 (Melpa), 20200402.919 (melpa), 1.1.1 (Melpa Stable), 0.9.0 (marmalade).
- csharp-mode: A major-mode for editing C# in emacs
-
Tree-sitter: an incremental parsing system for programming tools
Tooting my own horn, Emacs’ csharp-mode[1] is undergoing a rewrite to be 100% based on tree-sitter rather than regexps.
The new code runs way faster and is so much nicer to work with.
Once all the kinks are gone, I can’t imagine going back.
[1] https://github.com/emacs-csharp/csharp-mode/blob/master/csha...
- Csharpmode Adds Support For Treesitter
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?
tree-sitter - An incremental parsing system for programming tools
gtoolkit - Glamorous Toolkit is the Moldable Development environment. It empowers you to make systems explainable through experiences tailored for each problem.
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
tree-sitter-go - Go grammar for tree-sitter
elisp-tree-sitter - Emacs Lisp bindings for tree-sitter
tree-sitter-c - C grammar for tree-sitter
PHP Parser - A PHP parser written in PHP
tree-sitter-kotlin - Kotlin grammar for Tree-sitter
moose - Multiphysics Object Oriented Simulation Environment
parser - A Ruby parser.