News for hackers. Stuff that matters.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by guard-of-terra on Monday May 02, 2011 @01:49PM (#2507147)
How can he fit three-dimensional coordinates into a single 128-bit number? Seeing how he divides diameter, I assume he only took care of one axis.

I'm curious how many bits do we need to address a point in an universe with reasonable accuracy.

Re:Why floats suck - accurate galaxy-wide coordinates in 128... by CapitalistCartr on Monday May 02, 2011 @02:44PM (#2507352)
We'd need three axes to define a coördinate in space, four to include time. Given his estimation of the known Universe as 9.3e10 light years across, giving each axis 2^96 would yield an accuracy of about 1.1 kilometers, plenty enough for space navigation. Multiply that by the number of axes.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by jimktrains2 on Monday May 02, 2011 @02:57PM (#2507396)
yay! someone else who uses diæresis marks:)
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by eru on Monday May 02, 2011 @06:18PM (#2508141)
You should get a subscription to the New Yorker.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by gwern on Tuesday May 03, 2011 @11:34AM (#2510343)
> diæresis

You might want to see a doctor about that.

Re:Why floats suck - accurate galaxy-wide coordinates in 128... by rorrr on Monday May 02, 2011 @02:52PM (#2507386)
1.1 kilometers is not even close to being enough precision. That's way larger than your typical missile or a space ship. You can't deal with that kind of error and expect collision detection to work correctly.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by andos on Monday May 02, 2011 @04:50PM (#2507787)
It will never be the case, fortunately, that humanity will have to navigate a missile or spaceship across the observable universe (or the galaxy) with fixed point or otherwise.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by qntm on Monday May 02, 2011 @04:40PM (#2507746)
The interesting thing is that, as you get further and further from Earth or the Sun or the centre of the Milky Way, the level of precision which is even useful becomes less and less. What is one light year left or right for a quasar 13,000,000,000 light years away? Floats, then, behave entirely appropriately in this situation.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by cmaggard on Monday May 02, 2011 @03:00PM (#2507403)
He was indeed only specifying a single axis, just as you wouldn't use a single float to specify three axes.
Re:Why floats suck - accurate galaxy-wide coordinates in 128... by guard-of-terra on Monday May 02, 2011 @05:21PM (#2507888)
The number of scalars to specify a point in space varies from one to twelve and probably more - depending on the terrain.

For example, to point at objects reliably you need to factor their movement relative to gravity vector in.

I can totally imagine using just one (long) scalar, too.

Re:Why floats suck - accurate galaxy-wide coordinates in 128... by rorrr on Monday May 02, 2011 @02:50PM (#2507376)
You specify the accuracy you need. Let's say, 1 millimeter.

(9.3e10 light years) / (0.001 meter) = 8.79 × 10^29

log2(8.79 × 10^29) = 99.471

So you need 100 bits to represent each coordinate at that precision.