Bit like the hydra-headed water damage to my kitchen: Each repair seemed to reveal two more problems requiring non-trivial fixes costing time, money and/or ingenuity...

I won, but the hardest part was doing it right, getting it 'future resistant'...

Long ago, far away, I crafted lab & utility programs in 6502 Assembler and a bunch of BASIC dialects. Coding was easy, but clean coding was an order of magnitude harder. Worse if you were stuck with a snarl of badly maintained legacy stuff. Happens I'd the patience to comb out 'spaghetti', the wit to build in lots of flexibility...

I'm still on P_11. There's a lot of stuff I'd like to see in P_12 that probably won't arrive until P_14~~15. FWIW, there are bugs in my P_11's UI that I remember from P_4 !!

IMHO, Bondware / Rendo have a battle on their hands. There's so much catch-up & clean-up from the Smith Micro era, so many changes needed to support the new versions of Cycles & Python, all while sorta keeping up with several well-known 'game engines'.

Top of my wish-list are gas-gauge / trash collection, better handling of complex models, much more robust rigged FBX import and, perhaps, easy import of other rigged formats such as XPS and PMX. Comprehensible 'Cycles' would be nice: Is there a cross-platform 'For Dummies' in the house ?? My understanding is that the further future of Poser is critically dependent on getting unimesh working right. Right, mind. Which, in turn, requires lovingly marrying two very, very different rigging systems such that they 'play well' together. And, with that, importing other formats becomes so much easier...

YMMV.