The reason why I believe combining all of these will not be feasible is because in one of my recent conversations with Miller (and Miller please correct me if I somehow misremember here) he expressed his belief any project that exceeds N lines of code which I believe in this case it was something like 10000, it becomes unmaintainable and dies. Supposedly current pd codebase is at about 60 percent of that. That same code also lacks a lot of basic facilities like infinite undo and other core tools necessary for any kind of basic editing (given the nature of pd's structure it needs to exist inside the engine itself that is also responsible for stacking order). Features that have been added in pd-l2ork have added at least a couple of thousand lines of code with the externals and everything else obviously going well beyond that. As a result even if we prune the code and make a libpd which again implies Miller is okay with that (as in abandoning his version and building a new GUI app that interfaces with libpd), it is unknown whether we are going to be able to remain under the threshold required to meet Miller's goals. Personally I feel like Miller's wisdom should not be taken lightly but at the same time I prefer to choose the path of experimentation because it has proven so far very useful to me and therefore I would prefer to continue to run with it knowing very well that at some point in the future I just may hit a brick wall because I did not listen to his advice. In other words I am taking that risk because current benefits in my view far outweigh shortcomings and also because I expect to learn a lot in the process which will make any potential dead end look more like a crossroad. In my own work I simply do not have the luxury of time required for pd/extended to catch up with even half of the features that pd-l2ork currently offers. HTH