Currently Active Projects


Local chat is a very simple ‘irc-ish’ chat system over a Unix socket for a single computer/server. The target for this software is for headless servers allowing admins or other users to easily communicate on the console.

Development: Git Repository


Inspired by Tcl, Cutlet is designed to be a small and simple utility language to be used by other programs and projects.

Development: Git Repository


Meat is designed to be a very simple, high level and cross platform computer programming language for any with computer experience can learn and use.

This project is currently on hold. Unfortunately I was spending more time debugging the C++ code than developing features so I’m doing some testing with Cutlet and LLVM to create a language better suited for this project.

Development: Git Repository


Each project is currently hosted and managed on GitHub. Any issues, feature requests and security advisories are all managed there.

Contributing Source Code

With the projects being open source, source code contributions are welcome and encouraged. Before submitting source code here’s a small check list.

  • Comment your code and changes. It doesn’t matter how incredible your code may be, if we can’t understand it, it will not likely be added to the project. We have to be able to manage and maintain all the source code.
  • Being ad-hoc development, test suites tend to be an after thought, but before submitting a patch make sure it passes all the tests. If new tests are required, please feel free to add them.
  • Always be kind, courteous, helpful, friendly, welcoming…

Source code should always be submitted as a source code patch. Patches should be created from release software on the master branch. Here’s an example of the work flow using the cutlet project.

$ git clone
$ mv cutlet cutlet-myfeat
$ cd cutlet-myfeat

Make all your changes in the cutlet-myfeat directory. Note that each issue or feature that you develop should be kept is it own directory and separate from each other. If a change needs to be made and the patch recreated, it is kept clean from any other development. To create a patch use git diff as follows.

$ git diff > ../cutlet-myfeat.patch

Patches should be sent to Be sure the email title and body describe, briefly, the patch. If we don’t what the patch is for, it’s probably not going to get any attention.

Also if the patch is fairly small and resolves an issue on GitHub it can be attached to an issue comment.