I believe it is the same with travel. Some tech bros will plan their honeymoon with AI, yes, but choosing your favorite airbnb is sometimes part of the fun of a trip.
I do wonder if some company with money to burn and their backs against the wall will find a sympathetic judge in the argument that precedent be damned, clean-room implementations made with AI cannot be considered clean-room. It's too little too late to stop the rapid advancement of open tech, but that hasn't stopped courts from trying to send a message.
Maybe. But this article was at the least drafted by claude. It does all the things, including that weird word density + concept vapidity that makes parsing so difficult and annoying.
The "lie" is that some Bézier-spline drawing programs let you restrict on-curve points to a "symmetric" configuration where the control points are at an equal distance on opposite sides of the on-curve point, but this doesn't necessarily make the curve itself more symmetric or more smooth. The proposed alternative is to control the bend radius instead, and ensure that the curve bends the same on both sides.
It’s trading one property for another, isn’t it? Standard beziers with symmetric handles are C1 continuous but not necessarily G2 continuous; author’s scheme is the other way around, which makes them better for some use cases and worse for others.
The author was having a little fun calling it a “lie”, it’s more like a popular simplification. The question is how to join Bézier curves smoothly, and it’s fairly common for people to join them by matching the velocity, which means if you join two cubic segments (for example) with control points [a,b,c,d] and [d,e,f,g] where you’re joining at point d, then setting d-c == e-d, which puts c,d,e in a line with d as the midpoint, will connect the two curves smoothly. Lots of Bézier curve editing software will have a mode that enforces symmetric control points around the join point. The problem, or “lie”, is that this symmetric strategy doesn’t match the 2nd derivative, so there can be an abrupt change in curvature at point d. You can have a smoother join by adding constraints like curvature or 2nd or 3rd derivative matching, and that’s what the article goes into - one way of achieving smoother matches.
This WP entry mentions several other alternatives to smooth joins besides matching curvature:
either the agents are not good enough to do it, or they cost too much, or perhaps they refuse (i.e. seeing it as trying to subvert the intended function of the site or something).
reply