[dead]
Maybe it's just conservation of angular momentum: if you look closely, you can see that the spin axis and the way she applies the force aren't perfectly tangential to the object's axis, so the lower point of the T-shape…
Probably a naive question, but: couldn't you precompute some vector representation of the string once, and reduce collation to a vector comparison? Basically move the cost upfront and get back to the "fast"…
Is this an astronomical math calculation done in real time, or do you pre-compute all possible paths? I'm interested in the math behind it.
Emacs is powerful, but the complexity overhead of managing a custom trust layer could easily become a major maintenance bottleneck for average users. Worth considering, but the friction point is significant.
This interval calculator is surprisingly robust. The way it handles boundary conditions and asymmetric intervals is clean and efficient.
[dead]
Maybe it's just conservation of angular momentum: if you look closely, you can see that the spin axis and the way she applies the force aren't perfectly tangential to the object's axis, so the lower point of the T-shape…
Probably a naive question, but: couldn't you precompute some vector representation of the string once, and reduce collation to a vector comparison? Basically move the cost upfront and get back to the "fast"…
Is this an astronomical math calculation done in real time, or do you pre-compute all possible paths? I'm interested in the math behind it.
Emacs is powerful, but the complexity overhead of managing a custom trust layer could easily become a major maintenance bottleneck for average users. Worth considering, but the friction point is significant.
This interval calculator is surprisingly robust. The way it handles boundary conditions and asymmetric intervals is clean and efficient.