I really cannot get it.
With all due respect to Nuno and pscEx, winbuilder is NOTHING BUT a batch command processor.
There is NO particular "added value" in using it (as opposed to using batch, AutoIt, java or *any* other scripted language, including - as an example - the NSIS installer engine) if not for a few functions/addons that are handy to deal with the Windows NT platform.
There is NOTHING "revolutionary" not only in the "usage paradigm", but also in the actual "way of working".
The real value of a Winbuilder project is not the builder, but rather the contents of the project itself.
Whatever you want to build, the important part is to find out which values need to be edited in the Registry hives, what files need to be copied, etc., etc., then you can choose *any* scriptable language to have those needed steps be repeated automatically at each subsequent run.
Remember that in it's early incarnation Winbuilder was called "Batcher".
The great efforts and time profused on the code by Nuno and pscEx have contributed to make it a better tool, but it still remains a tool, nothing more, that can be replaced anytime with another tool, provided that one can "translate" to the new tool all the good contents of the various .scripts that a number of developers contributed, and a number of .scripts, for PE 1.x were anyhow derived/converted/adapted from BartPE plugins or however built upon info gathered through the BartPE experience.
So WHAT is the issue?
Someone wrote a new tool (doesn't matter if "better" or "worse" than Winbuilder) that can seemingly use the same .scripts Winbuilder use (possibly with a few small changes/adaptations).
At least till now, whilst Winbuilder in itself has been "closed source", all the .scripts have been (and cannot be other than, since being written in plain text the source and "code" are the same thing) "open source".
Unless Winbuilder and all the published .scripts had been released with the new foolish license
, there is no issue whatsoever, there is nothing "exclusive" in a current Winbuilder .script and everyone is perfectly free to re-use those .scripts as they are, or use the info in them to create a new script for a different batch processor.