4 ms·

Yes, Docker is great but learning it can definitely require more than 20 minutes. A `curl ipinfo.io` is still simpler.

deno 9y ago
This is the tax you’re paying for that every time: Connected to 35.165.108.15:443 HTTP/1.1 200 OK Server: nginx/1.8.1 Access-Control-Allow-Origin: * Content-Type: application/json; charset=utf-8 Date: Sun, 02 Jul 2017 08:54:40 GMT X-Content-Type-Options: nosniff Connection: keep-alive Body discarded DNS Lookup TCP Connection TLS Handshake Server Processing Content Transfer [ 4ms | 244ms | 518ms | 525ms | 0ms ] | | | | | namelookup:4ms | | | | connect:248ms | | | pretransfer:767ms | | starttransfer:1292ms | total:1292ms
- wittedhaddock 9y ago
  What tool (or arg passed to curl maybe) allowed you to generate that response? The graph is great
  - deno 9y ago
    https://github.com/reorx/httpstat https://github.com/reorx/httpstat It’s great for checking something quickly, otherwise you have the same thing in browser’s dev tools.
- gfodor 9y ago
  The OP was "baffled" why anyone would ever use this API. Clearly, the API's success shows that sometimes this tax you highlight is well worth it. (That was my point as well.) Nobody is claiming the tax doesn't exist, just that it shouldn't be baffling that a rational actor would choose to pay the tax in exchange for the corresponding benefits. (Not to mention with very minimal effort you can usually avoid the majority of the specific tax of latency you mention, by doing things like parallelizing the request with other work or doing it asynchronously to the user's interface.)
  - deleted 9y ago
    [deleted]

deno 9y ago

This is the tax you’re paying for that every time: Connected to 35.165.108.15:443 HTTP/1.1 200 OK Server: nginx/1.8.1 Access-Control-Allow-Origin: * Content-Type: application/json; charset=utf-8 Date: Sun, 02 Jul 2017 08:54:40 GMT X-Content-Type-Options: nosniff Connection: keep-alive Body discarded DNS Lookup TCP Connection TLS Handshake Server Processing Content Transfer [ 4ms | 244ms | 518ms | 525ms | 0ms ] | | | | | namelookup:4ms | | | | connect:248ms | | | pretransfer:767ms | | starttransfer:1292ms | total:1292ms

wittedhaddock 9y ago
What tool (or arg passed to curl maybe) allowed you to generate that response? The graph is great
- deno 9y ago
  https://github.com/reorx/httpstat https://github.com/reorx/httpstat It’s great for checking something quickly, otherwise you have the same thing in browser’s dev tools.
gfodor 9y ago
The OP was "baffled" why anyone would ever use this API. Clearly, the API's success shows that sometimes this tax you highlight is well worth it. (That was my point as well.) Nobody is claiming the tax doesn't exist, just that it shouldn't be baffling that a rational actor would choose to pay the tax in exchange for the corresponding benefits. (Not to mention with very minimal effort you can usually avoid the majority of the specific tax of latency you mention, by doing things like parallelizing the request with other work or doing it asynchronously to the user's interface.)
- deleted 9y ago
  [deleted]