Indeed. If a test runner embedding the Godot engine is now feasible on paper a proof of concept implementation seems deserved: if there are fatal bugs or limitations they will be eventually corrected (sooner if properly discovered, reported and discussed), and if there are none the new technology is "battle-tested" enough.
The article doesn't make that claim. For example, the service n7 is used by multiple other nodes, namely n3 and n4. There is no cycle there, so it's okay.
but why is having multiple paths to a service wrong ? The article just claims "it does bad things", without explaining how it does bad things and why it would be bad in that context.
Doesn't your advice contradict the BBC's phrasing? Collectively, the band lost its spot in the top ten. And, collectively, the crew has 35 seconds to prepare the stage for the next performer.
I think this is to some extent a British English vs US English thing; it's certainly more common to treat words like crew/company/etc as plural in British English. The linked article is being overly prescriptive, though. Both are basically fine.
I was mixing methods, sorry. My initial rendition for solving the cuts would initialise a somewhat sparse network from tree to ground, and solve for non-overlapping paths.
This became convoluted and I just opted for a far easier method of solving vector intersections.
Its also not perfect since I haven't factored in rotation origin very well, and I'm now pursuing a far simpler physics-based approach
reply