#!/usr/bin/perl

my $eyes = "closed";
my $heart = "aching";
my $beloved = "gone";

no warnings;

my $love = ();

open MY,"mind";
foreach ($love) {
    open MY,$eyes;
    tell my $mind or open my $eyes;
}

do not $fear and do not die;

$i; die "because i love you";

do { $i; sleep($_) } while ( $awake );

warn "$me" if ($i == $wrong);

bind my $love, $dear and do not exit;
for (my $world = "dark") {};
for (my $eyes = "blind") {};

Extracted from the Perl Poetry page.

I created a package for kanatest for the OpenZaurus (based on OpenEmbedded) distribution, and it has been commited to the OpenEmbedded repository for anyone to build and use. The following is a scaled down screenshot:

I have submitted a package to the Fedora Extras repository. It is kanatest, a small program to practice reading Hiragana and Katakana characters. My next mission: show this little program to my classmates and try to make them switch to Linux :-P. This is a screenshot of it:

What I learned on this session:

• More vocabulary.
• How to formally introduce yourself.
• More numbers. They are easy but are a little strange because Japanese use a system based on tens of thousands, for example saying 100,000 in japanese is jū man, something like ten ten thousands (10 ? 10,000).
• Diphthongs.
• The first Hiragana characters for the vocals: a = あ, i = い, u = う, e = え, o = お. This will need a lot of handwriting practice.

I readed at System.out blog the best description of how EJB 3.0 is taking shape, from who and from where it is copying ideas. I have used a few persistence frameworks, from in house developed, from designed for another non Java Language (Sparky from VisualBanker - Smalltalk) and the infamous VisualAge persistence framework (this one I thougth was what IBM submitted to the EJB 1.0 JSR group, because they are nearly identical and was available on Smalltak and Java editions), to Hibernate recently. My humble opinion is that this way to define a spec is the best one, let the implementors tell how are their solutions and take the best parts of each one.

The main topic of that blog entry is about the misconception that EJB 3.0 is Hibernate; it is not, but it can not be denied that Hibernate was one of the frameworks that helped EJB 3.0 take shape.