I am a little sad that CI has been failing for all commits merged to master in this repo since 9 Nov 2021. I often use that as an initial gauge as to the quality of a project, and I've got to say, this turns me off.
In this case it seems to just be an auth issue around building a docker image (and the first commit that failed was "Build and push dev image on pushes to master"), but it hasn't passed since, so this is not being tended to.
The miranda language (which predates haskell) had a zip function. According to wikipedia, miranda was released in 1985, but I dont know if zip was in the standard miranda environment back then. The comments in the source code say:
The following is included for compatibility with Bird and Wadler (1988).
The normal Miranda style is to use the curried form `zip2'.
> zip :: ([*],[**])->[(*,**)]
> zip (x,y) = zip2 x y
which suggests a slightly later origination of zip.
My manual VW Golf would like to have a word with you.
I don't drive in stop-start traffic, so I don't know how well it would work, but my manual VW Golf MK VII has adaptive cruise control. If you need to shift up or down, you just do so and cruise control re-engages.
I'm pretty much always in 6th gear when I've got ACC enabled.
The speed of light in a glass fibre is 2x10^8 m/s (according to Google). However the path through a fibre is not straigt. According to physics.stackexchange.com (http://physics.stackexchange.com/questions/80043/how-fast-do...), the speed of light though a fibre would be equivalent to 1.42x10^8 m/s.
Then you've got to account for the round-trip. You've only covered half the distance of the ping.
You also have to account for a non-direct path from London to Sydney.
All of this means you're looking at about 200ms or more as the lower bound, so your 10x becomes < 2x.
Fair point about only taking half the ping distance.
On the other issues, I disagree. They are the precisely the point of my objection. Assuming that latency is governed by the speed of light fails to take into account all of those other effects. Many of which can be mitigated. And, this is an extreme case. London to Sydney is probably one of the longest paths you can take (except maybe London Auckland?) with many stretches of fibre. On shorter paths, the overheads stack up much more heavily. In datacenters, the time of flight is a few nano-seconds, but the overall latency is tens of micro-seconds to tens of milli-seconds.
Isn't it odd that we accept 2x-5x (sometimes even 1000x) overhead over the best case and yet still argue that it's governed by the speed of light? How many other places in computing are we willing to accept that?
There is a "verbatim" mode of search that may help in these cases, which looks like it turns off a bunch of search heuristics. When you get your result, there's a "Search tools" button that reveals a dropdown that defaults to "All results". In that dropdown is a "Verbatim" option. Try that.
You can add the query parameter "tbs=li:1" to get verbatim results right away.
> "verbatim" mode... which looks like it turns off a bunch of search heuristics.
Ugh. This sounds like one of those families of PHP escaping functions: `escape_string()`, `really_escape_string()`, `escape_string_all_the_way()`, `no_really_i_mean_it_this_time_escape_string()`, etc. Google seems to have improved somewhat at fighting SEO spam, but their efforts to "helpfully" change queries have consistently made their service worse.
In this case it seems to just be an auth issue around building a docker image (and the first commit that failed was "Build and push dev image on pushes to master"), but it hasn't passed since, so this is not being tended to.