Re:iTerm2: Please disable 'Perform DNS lookups to check if U...
by 0culus on Tuesday September 19, 2017 @04:17PM
(#15288410)
I don't think it's worth throwing the baby out with the bathwater. But this should at a minimum be an opt-in feature, and not opt-out. Better yet, it's probably not needed. I've almost never needed to interact with URLs in a clickable way via a terminal.
[ Parent
| on HN ]
Re:iTerm2: Please disable 'Perform DNS lookups to check if U...
by joosters on Tuesday September 19, 2017 @05:22PM
(#15288935)
Clickable URLs are very convenient. I have plenty of code that runs on remote machines and generates data that I'd like to view in my browser. Print the URL out, and I can click on it to open it up.
n.b. for me, in iTerm2, I have to press cmd to make the links highlight before I can click on them - so there's little danger of accidentally opening something you didn't want to.
Doing any DNS before clicking on the links seems like overkill, though. My browser can tell me if the URL is garbage or not.
Re:iTerm2: Please disable 'Perform DNS lookups to check if U...
by sametmax on Tuesday September 19, 2017 @04:46PM
(#15288655)
I do but I always know if they are valid before I click on them, so I don't see the appeal of the DNS lookup. Plus that must be freaking slow.
Re:iTerm2: Please disable 'Perform DNS lookups to check if U...
by JosephRedfern on Tuesday September 19, 2017 @05:16PM
(#15288885)
Not necessarily slow, DNS Lookups are generally pretty fast:
~ dig somerandomurlimadeup.com | grep 'Query time: '
;; Query time: 23 msec
Re:iTerm2: Please disable 'Perform DNS lookups to check if U...
by greglindahl on Tuesday September 19, 2017 @06:57PM
(#15289488)
Er, that's just saying "you got lucky and the root nameserver you hit was fast". Looking up any valid .com requires that plus a 2nd level lookup.
Re:iTerm2: Please disable 'Perform DNS lookups to check if U...
by JosephRedfern on Thursday September 21, 2017 @04:35AM
(#15301548)
I tried on several domain names (that I had not, to my knowledge, recently visited), and they were all around the 25ms mark.
I'm not saying that this is the case universally, but for many the typical lookup time will be very fast.