I'm working on a short product(license) key generation and validation framework for Mac OS X based on elliptic curve digital signatures. The goal is to write a replacement for AquanticPrime (which uses long RSA signatures). It's based on OpenSSL.
I'm working on a programming language that has builtin support for reloading code at runtime. It'll also support various ways of modifying code at runtime, like with visual interfaces. The primary usage is for making interactive graphical apps, like games. Intro is here: http://andyfischer.github.com/circa/intro.html code is here: http://github.com/andyfischer/circa/tree/master
Looks like a cool little project. You should, however take a look at how most Lisps do something similar. You appear to be trying to take it farther than most Lisps do, but do have a look so as to not reinvent the wheel.
I've been working on K7, an extension library/framework for linking the V8 javascript engine with existing C/C++ libraries. Kind of slow going since work has gotten busier, but hoping to get back to it soon.
I'm working on implementing a hyperspatial text classifier in Haskell. It's conceptually similar to the hyperspace classifier in CRM114 (essentially a weighted nearest-neighbor search), but shouldn't crash as much or corrupt its data files. I've thought of some interesting problems to point a fast and effective classifier at that aren't spam detection.
I'm also working on a library/framework in Clojure for apps that process a folder full of files in some way. The idea grew out of a Clojure program I wrote to make a folder full of images greyscale (http://github.com/zakwilson/imagesieve/tree/master).
Wouldn't it be better to modify an existing, popular language to support this feature?
It would be better, but I want to do some cool things that I'm not sure if I can support in an existing language. One thing is automatically preserving state across a reload. This is really hard if I allow the programmer to store state any way that they want- I can't tell which things I should preserve. So the language forces the programmer to declare their stateful things in a special way. Another thing is introspec…
Unity is a game engine that uses Mono as its scripting languages. You can recompile on the fly (you frequently play the game in-IDE during development). All public variables are exposed to its inspector and survive this recompilation.
I'm working on a program that renders Julia/Mandelbrot set fractals using the GPU. I know there are a few other such programs out there, but I'm trying to make gpufrac really configurable. It has a bunch of features already (normal mapping and orbit traps are my favorites).
Git won me over when I found out that I could make all kinds of commits willy-nilly. I make a lot of small commits to my local repo throughout the day. At the end of the day I then take the time to go through them, merging related commits and removing stupid commits before I send my changes upstream. I've found that it's much easier to avoid breaking the build this way.