Daily Archives: April 22, 2009

Mamma Mia! Ubuntu is Global

I just noted someone reached this blog from Ubuntu-it.org, a Ubuntu site in Italy, in a discussion about Oracle and Sun.

One of the entries reads:

Oracle si pappa SUN

……chi vivrà vedrà……
Mamma mia….

This calls for a small cup of grappa.


Topic: ubuntu

Digital Open: http://digitalopen.org

Courtesy of a twit from Glyn Moody I just learned about Digital Open a new organization that, in its own words:

What can you make with technology that will change the world—or even just make life a little easier or more fun?

The Digital Open is an online technology community and competition for youth around the world, age 17 and under.

This is a great idea, so I have just signed up as “daveshields” and posted a brief note about myself.

I encourage others with an interest in this vital project to also join.

Open Source Dayenu: It Would Have Sufficed

We hosted a Passover Seder for almost fifteen people at our house early this month. We went to friends on the second night, and they had about the same number. Common to both was the singing of Dayenu.

Dayenu means “it would have been enough.” Here is part of the song:

Five Stanzas of Miracles

If He had split the sea for us.
If He had led us through on dry land.
If He had drowned our oppressors.
If He had provided for our needs in the wilderness for 40 years.
If He had fed us manna.

The theme of “it would have been enough” also applies to open source. When I try to explain why one should start a new open source project, as Philippe Charles and I did when Jikes was released as IBM’s first open source project, I make the following argument.

  • Start with code that is “good enough.”
  • It is not about the code, it is about the community that forms around the code.
  • If is not about the community, it is about the people in that community.
  • It is not about the people, it is about the relationships you can build with them.
  • It is not about the relationships, it is about the opportunities that may come your way because of those relationships.
  • It is because of these opportunities that you should engage in open source.

For example, because of Jikes it is fair to say that for most of 1999 I was known as the “open source programmer at IBM.” A few months into the year I got an email from someone who worked for one of the world’s largest banks. He said they had thought of a new project based on XML and thought IBM might be interested in collaborating on it.

I forwarded the email to someone in IBM who I though might be interested. I thought that was the end of it. However, a few years later, when I went to work for the Open Source Steering Committee, the group established to manage IBM’s open source activities, I went through the archives.[1] I learned that one of the first proposals ever presented was that of the bank.

I could find no record of how the matter was resolved, but that is not important. What is important it that an opportunity came IBM’s way only because of our work on Jikes.

Another example came in 2004, when I was able to save the job of an IBM colleague who was a well-known open source developer, by finding him a place on the Cloudscape/Derby team.

Early on in the Cloudscape/Derby days I got a note from someone at Zend, asking for the loan of a few surplus machines so that Zend could establish a professional development/certification program for PHP. Though I soon learned that IBM did not usually give away machines for this purpose, I knew that Steve Mills, head of IBM’s Software Group (SWG), was a strong believer in professional education. I also knew that PHP could play an important role in the Cloudscape/Derby effort. WIth the help of a colleague from SWG marketing I was able to secure the loan of five old laptops, and sent them on their way to Zend. At the time Cloudscape/Derby was still in progress, so I didn’t tell Zend my real motivation. I just said their request made sense and that they were welcome to the machines, and that IBM didn’t expect to get them back. [2]

In mid-July I learned the Doron Gerstel, then CEO of Zend, would be in New York City in a few days, and arranged to have breakfast with him in Manhattan. He began by saying he had been trying to establish a relationship between Zend and IBM for over a year, but had not known whom to approach. I said I was the person he was looking for, and then I told him about Cloudscape/Derby. He — or perhaps someone else from Zend — was present when IBM announced Derby at a conference a few weeks later.

Doron is now at another firm. I recently re-connected with him when I started to build out my LinkedIN network. I came to know many of the people now in my network through my open source activities, and I fully expect more opportunities will come my way because of them. Of course, I will also try to apprise them of new opportunities. For example, I learned a few days back that a company was looking for someone with expertise in compilers for VLIW machines, and sent a heads-up to one of my colleagues in the LinkedIN “Compiler Experts” group.

I could give many other examples, though I trust these few suffice to prove my point.

Here is an Open Source Dayenu:

  • If they had given us the code, it would have sufficed;
  • If they had built a community around the code, it would have sufficed;
  • If they had built relationships with people in the community, it would have sufficed;
  • If they had brought new opportunities because of those relationships, it would have sufficed;


1. As the Jikes days drew to a close, I said to myself, “Dave, you are lucky that Jikes was IBM’s first open source project, for IBM will probably establish some sort of process for future projects, and you won’t have to deal with it.”

Little did I realize I would become part of that process within a few years.

Having written “little did I realize,” I was reminded of the opening of a short story by V. S. Pritchett. It begins something like this: “I set sail for Ireland on a Monday morning. Little did I realize I was sailing into the fifteenth century.”

2. Zend never did send them back. One of my last acts at IBM was to explain why I could not return the five old laptops listed on the IBM property that I was responsible for.

On Programming: First SPITBOL LinkedIn Discussion From Galen Tackett

I started a new group for SPITBOL on LinkedIN a few days back, and today brought news that one of the members, Galen Tacket had started the first discussion:

It’s been a long, long time…

I last used Spitbol when I was still in college in the late 1970’s. I can’t claim to remember a great deal about it except that I thought it was a lot of fun to learn and use.

At one point I attempted to write, as part of a project for some course or another, an interpreter that would execute a subset of 6502 assembly language. Not machine language, mind you–I didn’t want to also write an assembler as well! It would have read a text file of assembly language and then parsed and executed it instruction by instruction.

This project was probably not a good idea in many ways, but it sounded like fun and my professor thought it was doable, so I tried.

I ran in to a number of big problems which prevented me from finishing within the available time. I’ve conveniently forgotten everything about the ones that were my own fault, but I remember having serious trouble with the Spitbol system itself, which was still relatively new on the CDC Cyber 174 NOS timesharing system we were using. Look at it cross-eyed, or make a slight syntax error, and it would give you an exchange package error–essentially just an octal dump of all the processor registers.

I wrote a thorough report on the project and got a B+ in the class even though this part of never worked.

I posted the following comment:


My apologies for your problems with SPITBOL/6000. I am its author.

Ah, “NOS.” I used all the OS’s for the CDC 6600, starting with the first, Chippewa. I think the *complete* manual was about twenty pages or so! My favorite was “Kronos,” though I may have the name wrong.

There is an interesting story about SPITBOL/6000. One day one of the systems programmers at the Courant Institute of Mathematical Sciences (CIMS) of New York University, noticed that part of the code for the CDC OS was clearly generated using a program written in SPITBOL. I checked my list of licensed copies (it was short: we sold at most thirty or so copies.) and found that CDC was not a licensed customer. I wrote a note to the CEO of Control Data pointing out the problem. An assistant to the CEO gave me a call shortly thereafter, and after I explained the problem, he promised to send a check. (I think it cost $1000 in those days). The check arrived a few days later.

SPITBOL has been released under the GPL. See http://code.google.com/p/spitbol

The binary for the IBM PC has been posted, so you can once again have fun — hopefully lots of it — programming in SPITBOL.

We should soon have binaries for Linux, courtesy of Mark Emmer

I am considering doing both a 64-bit version and also an implementation using LLVM.


  • Pages

  • April 2009
    M T W T F S S
  • RSS The Wayward Word Press

  • Recent Comments

    daveshields on SPITBOL for OSX is now av…
    Russ Urquhart on SPITBOL for OSX is now av…
    Sahana’s Respo… on A brief history of Sahana by S…
    Sahana’s Respo… on A brief history of Sahana by S…
    James Murray on On being the maintainer, sole…
  • Archives

  • Blog Stats

  • Top Posts

  • Top Rated

  • Recent Posts

  • Archives

  • Top Rated