Hmm... I'm not really sure how to address the issue. There are several things involved... first, uBrowser is being taken out b/c it just wasn't helpful. Somewhere along the line I actually made an alternate interface in core. TAPIr isn't being taken out, it's being folded in to remove the external dependency. It just isn't something module packages are going to use as is, and we barely use it in Ubercart.

Workflow-ng is being moved to Rules. A name change and reworking doesn't bother me and wouldn't keep me from using it. Mostly it comes down to needing something different, needing it quicker, and needing to remove the external dependency. I don't think anything we'll do would make an Ubercart site incompatible with Rules, but I do think that some things we need to do would be a lot harder just using Rules (insomuch as it is similar to Workflow-ng).

One example is evaluating stand alone condition sets that are setup through a form embedded into the taxes administration. Right now, someone has to create a tax rule then browse away to the Workflow-ng overview page and add rules to a tax to limit its application. This is unnecessarily complex and has caused plenty of headaches for folks setting up shipping. Doing this is already possible w/ our core conditional actions parser, and the UI is well underway.

Refer to point 2 in this post. We really appreciate all the work fago put into Workflow-ng and were to have found it in our early development of Ubercart. I just don't think it's good for Ubercart in the long run to outsource such an important part of the project.