Is the written documentation on the PB language not enough for you as an API? What more do you want? Unsure what sort of abstraction would be helpful to you, as it’s already abstracted in the sense that @wizard hides the low level stuff already. We don’t have access to the pixel buffer (yet), as an example.
Serious questions, as I’m trying to figure out why so few people seem to have discovered the power of PB.
A large chunk of the base isn’t coders at all (or not comfortable with how to get started).
I keep hearing people complaining about the math (which is more about the nature of computer graphics, 2D and 3d, and so on…)
Between the many existing videos/articles from the likes of Inigo Quilez, Dan Shiffman, Grant Sanderson and many more amazing educators out there, I’m not planning on delving deeply into the math anytime soon, except specifically to understand how pieces of PB work (so mapping, for one example, and it’s really hard to discuss sin(), let alone function like wave() without discussing the math behind them)
I realize I’m the exception to the rule, but I usually find myself so… I’m a self taught computer geek, math savvy, and I devour videos/articles like the above. PB lies in the intersection of a number of my interests, and perhaps I’m just lucky enough to fall into it with enough background and grasp of concepts that I pulled it all together. Understanding where other people get stuck is important but non-obvious to me, as I’m not there.