Airplanes might be designed in mm, but airports are most likely designed in metres, and whoops, suddenly you need to convert between the two.
Actually civil engineering as a whole is probably a relatively mixed bunch – vehicles drawings (when you need to design the infrastructure to fit specific vehicles for example) and other small-scale details might be dimensioned in mm, the standard curbstone naming system in Germany is based on centimetres, while infrastructure design itself (definitely including the CAD drawings) usually works in metres.
Vehicle drawings (maybe mechanical engineering in general) might be in millimetres, but a lot of civil engineering works in metres, so when designing some bit of infrastructure to fit certain kinds of vehicles, I do need to convert between the two, and the easier, the better.
For practical purposes there's the problem (at least a few years ago?) though that Akamai in particular uses DNS to steer you to the correct portion of its CDN and the default IPs returned by independent DNS resolvers tended to have relatively abysmal peering with the Telekom network that was getting completely overloaded at peak times.
Unfortunately "use <insert favourite DNS provider here> everywhere except for Akamai CDN, for which use the Telekom DNS" isn't something that consumer routers support, so you'd have to start running your own custom DNS resolver to work around that problem…
> Miles are great to estimate time of travel by car, take 1 minute per mile of distance on a highway and 2 minutes in the city and you will be pretty close.
That might be true where you live, but it's hardly a universal constant. 1 minute per mile might be sort-of-universal for long distance Interstate driving, but then again, you can just as easily phrase that as ~1 hour per 100 km in metric.
I'm rather doubtful about your 2 minutes per mile (= 30 mph average speed) figure for "city" driving, though – how's that even possible when urban maximum speeds are usually in the 25 – 40 mph range, and that's not counting time lost for traffic lights and other intersections, general congestion and parking?
Checking a few destinations around where I live in Germany, non-Autobahn cross-country driving is closer to 2 minutes per mile rather than 1 minute per mile (and highly variable depending on your exact destination, so no point trying to estimate driving times to the nearest minute, anyway), and never mind actual urban driving.
>That might be true where you live, but it's hardly a universal constant.
I have not said it's a universal constant, it's true in the US, where we use miles. ~1 hour per 100km is not as easy.
I cannot say I care much if you are doubtful, especially if you live in Germany and not in the US, I doubt many people in the US will care about your doubts too.
> Imagine some future hotel service trend where, right after the customer checks in, the checkin agent punches the customer in the face, by policy. I shouldn't have to check beforehand whether this is a "face punch" hotel or a "non face punch" hotel.
Reminds me of that Burkiss Way sketch where somebody wants to book tickets to a West End show, but they all involve the spectators being poked in the eye with a pencil:
The problem is that this breaks down if you don't want to leak any obscure subdomains you might be using via CT-logs – shared hosting rarely supports DNS-based certificate renewals for wildcard certificates, and even less so for domains hosted by an external registrar.
(Even for a fully self-hosted system you'd still have to figure out how to interface the certificate renewal mechanism with your DNS provider, so not as easy to set up as individual certificates for each subdomain.)
> (Even for a fully self-hosted system you'd still have to figure out how to interface the certificate renewal mechanism with your DNS provider, so not as easy to set up as individual certificates for each subdomain.)
That's exactly what the new DNS-PERSIST-01 challenge is for, being able to authorize a specific system or set of systems to request certs for a given FQDN and optionally subdomains without having to give that system direct control over your DNS as the existing DNS-01 challenge requires.
> I know that read/write conflict concerns are what got USB Mass Storage mode removed from Android, but surely there's some way to resolve that.
Depending on whether the respective kernel supported it, you were still unofficially able to switch removable SD cards into mass storage mode (though only with a rooted phone), although somehow, even if I remembered to officially unmount the SD card from Android first, it somehow still often led to mild filesystem corruption (luckily never anything fatal, though) that required regular chkdsk-usage.
> Or they could have figured out a new version of MTP that supports basic features like concurrent access and normal metadata. Or they could have gone for SMB/NFS over a virtual network link.
My current phone no longer supports the above mass storage mode-hack for the removable SD card, which annoyed me enough that I actually wrote my own SMB server app (https://github.com/buttercookie42/SimbaDroid), because all other SMB servers for Android that I'm aware of were either outright broken, unsupported, buggy or fiddly to use. Sadly the only open source Java-based SMB server only supports SMBv1, so you're stuck with that, and you still need root for full comfort, but within those limitations it works quite nicely.
Actually civil engineering as a whole is probably a relatively mixed bunch – vehicles drawings (when you need to design the infrastructure to fit specific vehicles for example) and other small-scale details might be dimensioned in mm, the standard curbstone naming system in Germany is based on centimetres, while infrastructure design itself (definitely including the CAD drawings) usually works in metres.
reply