That the very reason for choosing tos' Rubix Cube. As bad as the code is,

1. It is already, 95% or more OO structured.

   And none of the places where it breaks from good (in the Perl 5 roll-your-own standard of) OO mechanisms, are done for performance reasons. Just because tos didn't know how to achieve what he needed using those OO techniques, and wanted to get on with writing his application.

   If he could have let some framework do the OO bit of it, the rest is just fine.

2. It demonstrates that it is quite possible to write this kind of app using Perl.

   Right now. No C. No Java. No convoluted low-level optimisations. Just very ordinary Perl, that's (sort-of) OO to boot.

   No need to go learn another language. No need to give up all the things we all love about using Perl. Not even the need to resort to (and have to learn) Inline::C or PDL or anything else. It runs at a more than acceptable redraw rate. If only the OO were cleaner...

C'est la vie.