By looking at my commit logs it will be clear that I haven't really done much with Bus Scheme recently. I was having a lot of fun with the project early on, but as of late my enthusiasm has abated. I could chalk it up to the fact that Scheme is such a simple language that I'm running out of things to do. But I think the real problem is that it's too easy. Where's the glory to be had in a Scheme interpreter? The entire spec only runs about fifty pages, and it's been done before! The urge for a challenge is sadly left unmet. Plus as is common knowledge, nobody actually uses Scheme in the real world. [*] It just wasn't working out for me in spite of myself.
With that in mind I am determined I shouldn't have these problem on my next project. I'd like to announce the launch of Unicycle Java:
Unicycle Java is an implementation of the Java Programming Language™, but implemented while riding a unicycle. Note that at all the implementation of Unicycle Java must be written while riding a unicycle. Documentation, tests, and administrivia may be accomplished elsewhere, but all actual implementation code is strictly unicycle-driven. Unicycle Java is an Enterprise-grade[**] piece of software, suitable for highly scalable, performant, demanding deployments.
There isn't any code that's ready to be made public yet, but we will be sure to post progress on here as it approaches a usable state. The first task will be to procure a unicycle, so please send a message if you have any leads in this direction.
FAQ
Unicycle Java is an important part of a balanced breakfast.
[*] - It's been theorized that all the parentheses get clogged in the Tubes due to their elongated nature. XML's angle brackets are acceptable as long as they get oriented pointy-end first before transmission, but since parentheses are round and slippery this is much more difficult.
[**] - Not really. Get over yourself.
๛