Older blog entries for loadquo (starting at number 2)

Hmm, I wonder how well the diary portion of advogato will scale in the future. Will it still be readable and a viable platform for the exchange of views, for example if the number of diary entries increases a lot. What happens if between the time you log off, to the time you log on the number of messages puts your entry and any replies off the most recent diary pages, how will you find them?

It seems that it is being used for a whole mishmash of different purposes, from professional diary to personal, and a method of informal chat about advogato itself. Perhaps a more specialised approach would be a good idea, categories perhaps? Any ideas people?

Anyway, work on Codesoup is going okay with a seperate (slower) sub-project for visualisation and program design being near alpha release. A few problems include slightly different behaviour of the programs (they don't seem to evolve as fast) and trying to figure out automake so that it will include the sub-project and a known bug in the visualisation. Anyway once those are sorted it should be time for another release.

3 Jul 2003 (updated 7 Jul 2003 at 00:29 UTC) »

I am working on a qt interface for my project codesoup. It contains a custom widget that displays a representation of the internal state of the soup, and a few buttons for control of the actions of the soup. This should be hopefully useful for debugging the internal programs.

Next on the list of things that most need improving is the compiler for my own brand of assembler. Ideas include the ability to reuse sections of code (including passing in Symbol Information from the main file pseudo-functions).

I am also thinking about my real work, which is designing programs that alter, in a fairly random but clever way, a copy of themselves. Coming up with a few useful ideas, but none that seem amazing.

I have been working on the Frequently Asked Questions for my project, Codesoup, and because they are short at the moment, I decided to post them here

  1. What is the system It is a evolving system where programs compete for reward from a user. Currently the programs copy themselves and modify their offspring. The ones that get the most reward can overwrite other programs. There is also scope for cooperation between programs to solve problems.

  2. What would I use this for?
    Currently this is a research project, so researching is the order of the day. Once the research has been done hopefully it will be useful for complex online learning. By online, I mean the system will interface with the problem directly, rather than being presented with a lot of pre-specified training data.
  3. How do you see future development?
    Ideally it will become a community project and people will use it when they need to learn a problem that this sort of system can solve. The ultimate goal would be to produce a computer (possibly wearable) that used this sort of system as the operating system. Although that is so far in the future it is not worth thinking about at the moment.
  4. What success have you had so far?
    Limited, the system can evolve although at present the internal mutation operators are too destructive so evolution tends to remove the variation. This was a very primitive method of variation so it was not suprising.
  5. Why are you doing this?
    Because I don't think that the current way computer programs are developed is the only way or the best way for the user. So I am exploring other ways to create computer programs.

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!