The thing that's important to realize is that any open-source community has a will and mind of its own. In this case, the ACS/pg community lives and develops in a direction that we, the core developers, control only insofar as we are in sync with what the whole community wants.
If aD provided a more modular system where developing for the ACS no longer depends on "keeping up" with them, then ACS/pg has every reason to follow ACS/Oracle and to grow into a very successful open-source system. This is what I hope will happen.
However, if aD doesn't do any of this, and we are stuck with massive porting every time they release a new version, you'll see two things happen. First, the core team will disintegrate as the tremendous fun of porting outer joins and poorly abstracted Tcl code wears out. Second, someone out there in the community will start a new and better ACS/pg that *will fork* and become the product the community wanted in the first place. That's how open-source works. Darwinism at its best.
So, in the *interest* of the ACS community, ACS/pg will probably fork if aD doesn't do enough to be in sync with its own community.
