Created attachment 473562 [details] Performance benchmark Steps to reproduce: Math.hypot() appears to be significantly slower than Math.sqrt(). As it is a more convenient specialized method for calculating the hypotenuse, this makes it easy to write code that is accidentally less performant than expected. This affects our browser-based game engine Construct (https://www.construct.net) as well as third-party math libraries like glMatrix (who eventually realized the same thing and removed uses of Math.hypot(): https://github.com/toji/gl-matrix/commit/8962b2e7727594022e59e48e605049c69403da60) See attachment for what I believe is a fair benchmark. Note that optimizing the case where 2 or 3 arguments are passed should be sufficient to optimize the majority of performance-sensitive uses in game engines using 2D and 3D calculations. Actual results: On an Apple M1 Pro with Safari 18.1.1, after three runs, the Math.sqrt() benchmark completes in ~39ms, and the Math.hypot() benchmark completes in ~181ms (~4.6x slower). Expected results: Both benchmarks should complete in a similar time. If anything perhaps Math.hypot() should be faster, as more of the calculation is completed with a built-in method.