Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DNS over HTTPS

github.com

Post reply on HN
Print view View original

61–70 of 195 posts

Re: DNS over HTTPS

#61

Post by SEMW »

nijaru wrote: post #54
coinerone wrote: post #9

Earlier quoted context omitted.

"Performant" is a word in German. It translates to exact what "perfomant" would mean in english if it were an english word. The funny thing is, google translate, translates the german word "performant" to the english word "performant". https://translate.google.com/?hl=de#de/en/per%C2%ADfor%C2%AD...

It is not actually translating anything since performant is not considered a real word in English, although I commonly see it used in the tech world.

> performant is not considered a real word in English, although I commonly see it used...

This is close to being a contradiction in terms. The purpose of words is to communicate, and if a word is being successfully used to communicate -- which clearly it is -- what exactly does it mean to say that isn't "considered a real word"?

Also, "Considered" by whom? The dictionary? Dictionaries are descriptivist -- they record usage, they don't prescribe it [0]. If it isn't in the dictionary yet, that's only because the usage hasn't been used widely and/or for long enough that it meets the inclusion criteria [1].

(As it happens, "performant" is at the stage where it is starting to pass those thresholds, and is now in the OED [2])

[0] http://englishplus.com/news/news1100.htm

[1] http://public.oed.com/about/frequently-asked-questions/#qual...

[2] https://en.oxforddictionaries.com/definition/performant

Re: DNS over HTTPS

#62

Post by geofft »

politelemon wrote: post #3

> for privacy, performance and security. I understand the privacy and security aspects. But I am wondering - how can DNS over HTTPS be more performant in the case of curl commands? A browser could probably persist the connection to the resolver and issue several requests together, but with a single curl command surely there's the overhead of initiating the first DNS resolve, the HTTPS connection, the second DNS resol…

If your ISP is intercepting DNS requests and sending them to a slow or broken server, DNS over HTTPS ensures this won't happen. (Yes, they could block the traffic entirely, or slow it down for fun, but they can no longer intercept and redirect it.)

Re: DNS over HTTPS

#64

Post by mohamedattahri »

metafunctor wrote: post #26
CogitoCogito wrote: post #7

Earlier quoted context omitted.

> Side note - I just learned that performant is not a recognized word ( https://english.stackexchange.com/questions/38945/what-is-wr... ) I don't personally use the word since there are many alternatives, but its use is now definitely widespread and consistently understood. There's really no argument against the fact that it has entered the English lexicon.

Can anyone give examples of cases where “performant” would be better than “efficient”? To my mind, the difference is that “performant” delivers results quickly, whereas “efficient” uses little energy. A performant solution might be efficient, but not necessarily, and vice versa. Does anyone else share this understanding or am I living in a linguistic bubble? Not sure about Swedish (Daniel is Swedish), but in Finnish,…

In my understanding, performance is based on the value of a measure improving in one way or another.

Efficiency is relative to the amount of resources required to achieve a similar result. To use the car example above, a car that can do 100km/h at 4L/100km is more efficient than another can than do 100km/h at 8L/100km.

The point of absolute efficiency is referred to as optimum. Essentially, top performance possible with the minimum of resources possible.

Re: DNS over HTTPS

#66

Post by ce4 »

kabes wrote: post #60

You can also do http(s) over DNS: http://code.kryo.se/iodine/ . Nice way to avoid paying captive portals, although probably not legal.

What does this shady technique (dns tunneling) have to do with dns-over-ssl?

Re: DNS over HTTPS

#67

Post by billpg »

kabes wrote: post #60

You can also do http(s) over DNS: http://code.kryo.se/iodine/ . Nice way to avoid paying captive portals, although probably not legal.

Can I do HTTP over DNS over HTTP over DNS over HTTP over DNS over HTTP over DNS over HTTP over DNS?

Re: DNS over HTTPS

#68

Post by kuschku »

kodablah wrote: post #57
kuschku wrote: post #55

Earlier quoted context omitted.

Easier to prevent censoring from the ISP, but you're now just reliant on another company's systems. If you just want a solution for having a remote server execute DNS queries for you, you can just use any of the existing VPN protocols purely for DNS resolution, or even make a better performing version. All that overhead HTTP adds is wasted for this.

> All that overhead HTTP adds is wasted for this. When you're in an area where your DNS provider is limited by the state, you won't consider it wasted. But if you're not and you do consider it wasted, don't use it. But saying it doesn't seem to provide any benefit is wrong and just telling people to use a VPN for DNS resolution is also wrong (at least until the ergonomics improve).

It's more a question why a company like Google would pay several engineers who are paid 6-digit sums to build this when they could build for the same or less much more powerful solutions.

Re: DNS over HTTPS

#69

Post by banachtarski »

billpg wrote: post #67
kabes wrote: post #60

You can also do http(s) over DNS: http://code.kryo.se/iodine/ . Nice way to avoid paying captive portals, although probably not legal.

Can I do HTTP over DNS over HTTP over DNS over HTTP over DNS over HTTP over DNS over HTTP over DNS?

You do realize DNS is not a fully featured protocol right...

Re: DNS over HTTPS

#70

Post by userbinator »

CogitoCogito wrote: post #7
politelemon wrote: post #3

> for privacy, performance and security. I understand the privacy and security aspects. But I am wondering - how can DNS over HTTPS be more performant in the case of curl commands? A browser could probably persist the connection to the resolver and issue several requests together, but with a single curl command surely there's the overhead of initiating the first DNS resolve, the HTTPS connection, the second DNS resol…

> Side note - I just learned that performant is not a recognized word ( https://english.stackexchange.com/questions/38945/what-is-wr... ) I don't personally use the word since there are many alternatives, but its use is now definitely widespread and consistently understood. There's really no argument against the fact that it has entered the English lexicon.

I don't use it either, and I agree with the poster on that stackexchange link about it sounding like manager/marketing-speak, but when I see it, it makes me pause for a second to think about what really means (perhaps that's the point) --- I had this exchange with a coworker not long ago:

CW: ...and this way it'll be more performant too.

Me: Performant? As in faster?

CW: Yes.

Me (to self): Then why didn't you just say it'll be faster?

IMHO it obfuscates meaning and should be avoided; the surrounding discussion/vagueness about what it means (I don't think it means efficient, but only faster --- as in, a high-performance car) shows that too.

Post reply on HN