CodeParadise
Moose
CodeParadise | Moose | |
---|---|---|
3 | 2 | |
79 | 133 | |
- | 0.0% | |
9.3 | 7.7 | |
4 days ago | 22 days ago | |
Smalltalk | Smalltalk | |
MIT License | 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.
CodeParadise
-
CLOG And The Competition
I think these projects could be comparable: - JustPy for Python. - CodeParadise for Pharo Smalltalk. But I cannot go into details, because I don't have enough experience with those, only with CLOG.
- Fabrik a Visual Programming Environment
-
SqueakJS – A Squeak VM in JavaScript
Instead of having a Smalltalk image which contains the typical GUI (Morphic or otherwise being BitBlt on a HTML Canvas) I run a Smalltalk image which has a number of Classes representing WebComponents. These classes have a small interface with Javascript (implemented as primitive calls in case you are familiar, similar to other SqueakJS plugins). When instantiating such a WebComponent, it will also instantiate a DOM element (the WebComponent). Events in the browser are wrapped in Smalltalk event classes and will be given to an event handler process (Smalltalk process) which will do the relevant work. So for example drag and drop is implemented fully in Smalltalk. My code is free to use. See https://github.com/ErikOnBike/CodeParadise
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?
opensmalltalk-vm - Cross-platform virtual machine for Squeak, Pharo, Cuis, and Newspeak.
gtoolkit - Glamorous Toolkit is the Moldable Development environment. It empowers you to make systems explainable through experiences tailored for each problem.
pharo - Pharo is a dynamic reflective pure object-oriented language supporting live programming inspired by Smalltalk.
tree-sitter-go - Go grammar for tree-sitter
PharoChipDesigner - A little chip design game inspired by KOHCTPYKTOP: Engineer of the People by Zachtronics
tree-sitter-c - C grammar for tree-sitter
pharo - The Sources for Pharo
csharp-mode - A major-mode for editing C# in emacs
lqml
PHP Parser - A PHP parser written in PHP
Cuis-Smalltalk-Dev - Active development of Cuis Smalltalk
tree-sitter-kotlin - Kotlin grammar for Tree-sitter