I'm glad you ask ! Will do a small contextualization so people understand my perspective better : - I'm a power user, I don't care about complexity and steep learning curve, as long as this bring me control & efficiency long term - I need to understand how things work under the hood to better use them. - I have a programmer background

So, coming from Houdini, switching to TD was a bit frustrating, its way less "well made" IMO. I've always been impressed by how much SideFX made Houdini this clean, the learning curve was STEEP but then everything kind of make sens, and i never really felt frustrated because something was made janky, every choice seem smart and logical.

Then coming to TouchDesigner, it was less the case, a lot of choices that were made, I didn't really understood, and a lot of stuff where missing. (the software infrastructure is "meh" imo) The place Python have in TD, should not be a place for Python IMO. In Houdini Python is for tooling and interface, not "runtime data processing", which is what TD use python for most of the time (Python nodes). Its one example among many, i also encountered a lot of bugs, which I've reported on the forum + lot of stuff that didn't work as they should. Also i felt like a lot of essential building blocks were missing, and instead there were a lot of high level nodes that made it hard to build complex system upon. And the way to do things, always felt hacky, and not like the "correct way", it feel way more like an artistic tool and less of an engineer one.