In the desert, you often really don't want to be walking midday, but if the moon is out doing 20 miles in a night isn't too bad, and doing it split over two days is fine. 5 or 6 liters of water plus some food would be plenty, depending on what you have available to carry that ~15 pounds splitting into two days may be more comfortable. Either way, infinitely less risky than building a motorcycle.
4 mph takes talent, especially over distance. Andthat’s on hard surfaces. From what I understand walking on sand is deceptively taxing. I’d say 2-2.5 and not as the bird flies distances. So ten to fifteen hours of walking if your feet let you.
The desert in question isn't all sandy dunes; there's a lot of rocky or compacted surface (see photo), so you can make pretty decent time (but yeah, sustaining 4mph would be pushing it for most people).
There were far, far worse things out there than Subversion. VSS, ClearCase, an obscure commercial one written in Java whose name escapes me now..
Subversion was basically a better CVS. My recollection is that plenty of people were more than happy to switch to CVS or Subversion (even on Windows) if it meant they could escape from something as legitimately awful as VSS. Whereas the switch from Subversion to Git or Mercurial had more to do with the additional powers of the newer tools than the problems of the older ones.
Hmm, maybe Microsoft Visual Source Safe? I remember that. It was notorious for multiple reasons:
* Defaulted to requiring users to exclusively 'check out' files before modifying them. Meaning that if one person had checked out a file, no one else could edit that file until it was checked in again.
* Had a nasty habit of occasionally corrupting the database.
* Was rumored to be rarely or not at all used within Microsoft.
* Was so slow as to be nearly unusable if you weren't on the same LAN as the server. Not that a lot of people were working remotely back then (i.e. using a dial-up connection), but for those who were it was really quite bad.
I'd be very curious to see exactly what 'fixing' the eye movement actually looks like. Like are they always staring directly into the camera? Or are they sometimes randomly looking around all over the place? Cause that would look totally normal..
If you don't, that's fine. But is it really necessary or desirable for -ffast-math to silently break isinf() and isnan()? I don't think it's inconceivable that some people might need those.
I mean, I can write my own implementations, but it seems kind of silly that I should need to in the first place.
I think the risk is that unless people think that reporting a bug there might actually cause it to be fixed, few will bother to report bugs and you'll end up with mostly people just venting, thus perpetuating the cycle.
That's a shame, we've bought two Bosch dishwashers (two different houses). The second one is 12 years old and still working. Had to replace the pump once, although that problem was almost certainly caused by sediment in our water lines.
I like that they've been quiet and reliable, the reliability affirmed by the repair person that replaced the pump.
reply