R3.0 Plan for July 2009
Progress on R3 continued to accelerate during June, thanks in large part to an even greater level of contribution from the REBOL community.
Many significant issues were resolved... "nagging" issues like the relationship between binary and string and how do you compare at different levels between datatypes. The result is a more robust and powerful REBOL. And, if you're standing on the sidelines wondering what's going on, all you need to do is glance at CureCode or the R3 change log to observe the advancements that are being made. Good stuff. My hat is off to everyone who helped make this progress possible.
Last month, for a primary goal, I wrote: "It is essential to get the plugin system running this month." Well, it didn't happen. At the heart of the problem are concerns about decoupling -- how to isolate the REBOL kernel from the plugins. This isn't easy. (In fact, I was reading about Google Chrome recently, and they mention similar issues in their system.)
For example, if next year we decide to add a new internal datatype, we don't want to break all the plugin modules. Such breakage would occur if the plugins use a direct method of recognizing datatypes. The more I think about this, the more I think it is a critical issue.
The way to make progress on this issue is to break it down into smaller chunks, get it out to users, then carefully build back up what we need (and desire). A lot of the code is already in existing releases, so what remains to be done is less of a coding issue, and more of a definition and documentation issue.
Goals for July
Here's the master list: