[Sooc-devel] why Sooc?

[Mike R. <mik...@gm...>]

I've invested rather a lot of time into this project.  Certainly it
accounts for the vast majority of my coding time over the past year or
more.  The base system of Sooc is more powerful than ever, and the
accompanying class library is steadily improving.  But now I'm
wondering, as I have on occasion before, whether Sooc is a productive
endeavor.

I thought of a real test of Sooc's usefulness.  We could rest assured
that it is a Good Thing if we (or I) port a C++ or Java project to
Sooc and the result is more manageable code.  If the code just grows
uglier or more confusing, it is a pretty safe bet that Sooc is only
valuable as an exercise in OOP.

I don't propose halting development.  In fact, I have a few important
ideas about the collections module that really should be implemented.
Nonetheless, I want to start working in parallel on a port of some
existing code as soon as possible.

Any thoughts?  Ideas as to which code to port would be especially handy.

-Mike