Here is a visualisation of such a topic map:

Ok, ok, one map thing after the other:

Somewhat with little enthusiasm I marked today the recent exam for the semantic web course I had given this and previous year. What kept me going was the fact that this is not only the last exam for that particular course, but that it is also the last course for me, hopefully for a very long time.

The course had not been difficult or anything, quite pleasureable actually. And as usual I also experimented with new ways to explain stuff, new material, new tasks, and new exam question.

Having decoupled myself from the standardisation process had an extremely beneficial consequence: I could push my own TMQL implementation forward.

I commented out some of the cruft which I only maintained to keep some co-editors happy. Among the prominent victims is the SELECT clause which is by far the most convoluted flavour of TMQL. I also removed all references to CTM.

I was just finishing up my last Perl test case for the day, when CatBert hopped onto the table. He sat down just behind the laptop screen and fixated me.

He knew exactly that this drives me crazy as we had been playing this game before. Obviously he wanted to tell me something.

Category Economy

That one I find just brilliant. Unfortuntely not from me. Cudos to the unknown originator.

Before I submit a bug report , has anyone observed the memory usage pattern of Storable?

What Happens?

First I create a hash with 30 megs of memory:

having afterwards a process (virtual) size of ~50 MB.

Then I use Storable to freeze that:

Even though

It is now about a year that my wife has taken over the small trophy family business Barta Pokale.

It has been a steep learning curve for us as the long-established business suffered from several legacies. Now that we removed most of it and turned the business around, we have started to modernize the portfolio.

On CPAN there are few options for reactive, event-driven programming, POE being just the most prominent one.

One hidden gem in this category is IO::Lambda. Given that it uses strongly a functional paradigm and continuations it will probably alienate most procedurally wired brains. The documentation and the examples are rich, but that itself presents a high entrance barrier.

Back in business.

Category Society

I am now in the process to move a number of CPU intensive jobs into Gearman workers.

What Is

Unfortuntely, the required boilerplate code for that is quite crufty:

First, inside your workers you are supposed to do this:

That object is not what it appears to be. It is not a worker, but actually the handle to the job server.