i dont know anything about DAZ, i just know from a developers point of view it makes a lot of sense to build your code in such a way that it can easily be used and re-used for multiple applications.

What would be the use of building a new procedural texture engine for DAZ studio if they already have one laying around in the bryce code? 

In fact, if multiple programs use partly the same code base, updating that part will benefit both applications.

There are many practical applications for sharing code amongst different pieces of software.

For instance:
Google Chrome, and Apple's Safari webbrowsers both use the same "webkit" html rendering engine.
When the webkit development team creates updates, and google and safari integrate the new version of the webkit engine in their browser, both browsers gain the same improvements.

I apply this same strategy as well in my own day job. For example, I make use of the same pdf engine in multiple pieces software.
And just last week i was able to build a front end for a client of a client of mine to safely represent them part of the information in my clients intranet to their client, in one afternoon. Purely by salvaging and re-using part of the intranet code.

It could well mean that DAZ is trying to channel their resources. They did say they were short of developers, so it makes sense that they try to salvage the most useful parts of their different softwares, and apply them as efficiently as possible across their product line.

(_/)
(='.'=)
(")(")This is Bunny. Copy and paste bunny into your signature to help him gain world domination.