I think a real problem is that /COMMAND has put the community into Fear
Uncertainty and Doubt
mode. Because /COMMAND is coming no one wants to work on /COMMAND, but
/COMMAND never comes.
The Web site says:
{
REBOL/Command will be released soon. It is for commercial users who
require additional features
to access business systems or legacy applications, including database
connectivity or native API
access
}
Does this mean it will include connectivity with mySQL? Dunno.
After the /VIEW beta hits the street, and the RT guys take a much
deserved rest, I think we need
to make a concerted effort to get some official high-level details
about /COMMAND. For example,
what databases it will connect to and what the API interface will look
like? If we knew that
much, then some work at least could be done on complementary products.
This would also be helpful in testing /VIEW. The most obvious niche for
/VIEW is business
applications, which often depend on database connectivity. With at
least the API specification,
we might be able to try dummy programs to see well they would hook up
to the API.
Meanwhile, a few of us have started work on turning REBOL.ORG into a
user-supported Web site. One
of the things we will do is manage the scripts used on the Web site as
open source. We also have
RT's blessing to form a working group to enhance SELMA. If we can show
how well this community
can work together on open source scripts, perhaps it will help shake
loose the /CORE code.
-Ted.
