Here, the final product:
Divider VR 10.gh (285.3 KB)
Yes, it is slower than the curve-line intersection solution, but it’s not so bad. With the current set of curves it takes approx. 7 secs to process. I guess it is as @Fabio_Franchetti says:
that it is a question of what you value or need more; brevity and clarity of purpose or speed. I suppose if you were coding a component, you would avoid the boolean difference for the speed and because you don’t read anything of how the coding component works from the outside? But I wouldn’t know.
In the above post, the Anemone loop is an artifact of me trouble shooting. It’s not needed, but it is useful in the sense that it prevents the screen from stalling, and gives a visual indication in the model space of how far along the script is.