(We needed to wait until the second spacecraft was three decameters away before firing the main rocket engines, not three decimeters, but someone typed in in wrong and that's why we lost the second spacecraft)
That's why you don't use decimeter *nor* decameter. All specifications have to be in meters or millimeters. And for larger distances maybe in kilometers; though '5000 m' is a perfectly fine specification.
Hand b) Windows and Mac have the same problem (SDL, GTK+, etc, and the dlls have to be included with the binary downloads because Windows/Mac don't have an easy to use package manager).
Not quite sure what you are talking about, but... applications on Mac OS X generally do not need to include any GUI toolkit. The toolkit is part of the OS.
That's also the reason there is no package manager - because you don't need one.
(Applications that use a non native GUI toolkit - like GTK+, wxWidgets etc. - will run into the problems you described. But those are not the norm on OS X. And they stick out like a red headed stepchild anyway.)
(We needed to wait until the second spacecraft was three decameters away before firing the main rocket engines, not three decimeters, but someone typed in in wrong and that's why we lost the second spacecraft)
That's why you don't use decimeter *nor* decameter. All specifications have to be in meters or millimeters. And for larger distances maybe in kilometers; though '5000 m' is a perfectly fine specification.
an inch seems like a more reasonable unit of measure than a centimeter, which seems too short.
Um. Why?
And a foot is also a useful measure, of which there is no corresponding metric unit.
We just use 30 cm. Not that hard, really.
Hand b) Windows and Mac have the same problem (SDL, GTK+, etc, and the dlls have to be included with the binary downloads because Windows/Mac don't have an easy to use package manager).
Not quite sure what you are talking about, but ... applications on Mac OS X generally do not need to include any GUI toolkit. The toolkit is part of the OS.
That's also the reason there is no package manager - because you don't need one.
(Applications that use a non native GUI toolkit - like GTK+, wxWidgets etc. - will run into the problems you described. But those are not the norm on OS X. And they stick out like a red headed stepchild anyway.)