In short, it’s a language-parametric source code index and search algorithm. I put together a prototype in python early last year, and have been working on a port to scala in my free time since then. The scala version will begin to be demo-able in the next couple of weeks. This will be followed by several months of deeper research into scalability and performance.

I’ve met a few of the founders, but hadn’t seen much conversation between them until recently. I take this as some confirmation that the line of thought I’ve been pursuing for several years does in fact have some cohesion. Eelco Visser at SLE 2008/09 (and his lab at TU Delft), Markus Voelter at EcilpseCon 2008, and Steven Kelley who has commented on this blog in the past.

I’ll not likely have time to prepare a submission to the contest, but I’ll certainly be following it and if it does become a part of some conference, I’d love to attend.

Of all the topics and academic or professional software engineering, I think this one cuts right to the heart of the remaining productivity bottlenecks in software engineering. I’m happy to see this talented community gaining momentum.

I’ve been bumping into category theory repeatedly for many years, and it seems like something I’m going to have to master eventually.

A few years ago I recognized that one thing missing from all the computer science education I had received was a mathematical tool that allowed me to treat languages as objects. It only occurred to me after taking several classes on the syntax of natural languages. I had seen deep mathematical treatment of various aspects of languages, but none that allowed me to refer to a language with a symbol (except maybe as a set, as was the case in my undergrad formal languages class).

After dancing around the subject for years, it’s pretty clear that Category Theory is the tool that I’ve been looking for. I’m looking forward to exploring its concepts.

A colleague of mine sent me a couple of related links: A series of youtube posts from the “Catsters”

And a paper on physics & topology

It had to happen eventually. I’m still planning on playing a little in this space — starting with some web-based python tools — but it looks like it may be crowded soon.

I still expect that I’ll be writing java in the future. And there is room for serious time spent with ruby or haskell. But I think python is probably replacing the niche that perl filled for me. So long, old friend.

I spent some time in the last couple of days with the inspect module. The result is some simple analysis of the python 2.6 code that happens to be installed on my laptop. Next rainy day I’ll look at compiler.ast and parser to make this a lot more interesting.

Monads in python with nice syntax

Linq in C# is a monad

the monad laws (haskell)

a gentle introduction to haskell: values and types

comparison of parser generators (wikipedia)

method signature type checking decorator for python 3.0

dynamic typing vs dynamic language (groovy)

GLR parser

More editorial and a general update to follow soon (including some thoughts on SLE 2008)

It’s about twice as expensive as the old machine I was renting, but the service wasn’t so great and this gives me the chance to gain exposure to a popular compute cloud.

Now if I can just build a popular website that actually takes advantage of the easy scaling…

So the obvious question given the earlier posts: Where’s my monitoring? What’s the right place to set that up? Not that I really need any for this blog, but if I were running a real site, I’d be asking that question right about now.

• Spacewalk
• Cobbler
• Puppet(not a RH project, but it seems to have quasi-official approval)
• Func
• TheHat
• Genome

The “Genome” project looks like some kind of umbrella or glue for puppet, cobbler, and func. Cobbler now has spacewalk integration on its near-term road map, so things are already starting to come together. Looking forward to whatever “genome” becomes.

Somewhat related: I see that RedHat and Amazon’s EC2 have some sort of official relationship. I started looking at EC2 last night, and think Amazon’s done a great job of abstracting out all the messy parts of administration. I wonder how much of the RH projects mentioned above are intended to manage ec2 clouds? I would love to see some spacewalk graphs of a set of ec2 instances. Is anyone on the spacewalk team writing ec2 plugins?

While searching for more alternatives, a colleague noticed Spacewalk. It took me a while to realize what this was. Could it be all the NOCpulse code? One git clone git://git.fedorahosted.org/spacewalk.git/ later, I was seeing a lot of familiar code.

In 2002 Red Hat acquired NOCpulse shortly after I left for UCLA for grad school. Looks like six years later they are open-sourcing all the code they acquired. There’s some discussion about telling a fuller story of this code, including a list of alumni contributors.

I’m anxious to see where it goes from here. Open source tools in this area are sorely lacking — is Spacewalk the answer? I’ll likely be posting a lot more about this in the future.

I was already thinking I was going to need this, but now it’s clear that I need my own QVT/OCL implementation. I may not need all of it right away, but at minimum I needed a parser. A couple of months ago I used Medini QVT as a reference implementation to create a couple of demo transformations. Now I’ve gone through the OMG specs to extract the grammars and have created a single large antlr grammar. The QVT portion worked fine, but of course adding OCL introduced a lot of left recursion.

Enter OMeta, which can handle grammars that contain left recursion. Turns out that the author Alex Warth is participating in this design lab as well. He’s put a lot of work into a javascript version of OMeta. I would use it directly except that I want to have deep interaction with EMF and Subversion. And potentially a lot of other java code.

As of a few minutes ago, I think I have my solution: Implement a java wrapper for OMeta using Mozilla’s Rhino. We’ll see how cleanly I can wrap it.

I’ll try to be good about posting updates on this. I have some hard deadlines approaching, but I think this project is now in the critical path, so it’s likely that it will get done soonish.