News for hackers. Stuff that matters.
Re:Air traffic failure caused by two locations 3600nm apart ... by jjk166 on Wednesday November 20, 2024 @12:26PM (#42196207)
I don't think it would be too difficult for a computer to handle. We already deal with situations like float(1) = int(1), it doesn't seem any harder to handle torque(1) = energy(1).
Re:Air traffic failure caused by two locations 3600nm apart ... by eru on Wednesday November 20, 2024 @08:43PM (#42200190)
The problem is that you want torque not being equal to energy.

Specifically you have:

torque = force * distance

energy = force * distance

The only difference being that in the former the farce is perpendicular to the distance, and in the latter it's in line with the distance.

A vector based system could distinguish the two, but you don't always want to deal with vectors in your computations. (And I'm fairly sure there are problems where even using vectors ain't enough to avoid this problem.)