Comment by eyelidlessness | Hacker News Reader

Comment by eyelidlessness | Hacker News Reader

Parent Full thread

> Istio

Also looks like a trivial config change. I’m not familiar with it but I don’t see any red flags.

> If it's not broken, don't fix it :)

This seems exceedingly myopic in this context. Why migrate to broadband from 56k modem? That modem connects to the internet too! Why upgrade to a browser version which supports HSTS? You can just manually type https in the location field. Why try anything with new features at all? You can just never have new features if they work.

I’m not saying there’s never a trade-off with any of these things. But you’ve preemptively ruled out any benefit without exploring them… or whether they even have any meaningful (to you) cost. “Cutting off your nose to spite your face” is the phrase my family uses for this.

There is a difference between switching protocol, and:

  - not migrating to broadband from 56k modem
  - not upgrading to a browser version which supports HSTS
  - not trying anything with new features at all

HTTP/1.1 still serves its purpose, successfully, without any impact on performance/usability. I'm not Google, I'm not serving a webpage to 8 billions devices at the same time.

Sure I can try HTTP/2 (and I did), and HTTP/3 (and I will). But when it comes to distributing an application/service to customers, I'll automatically choose the battle-tested 30 years old technology which is supported by everyone and every device.

Okay enjoy your slower than necessary web stuff for no apparent reason!

There are a few small, but important cases where h2 in the mix could possibly bite you.

In my case it's monitoring security issues like h2 to h1 header smuggling and the security implications in complex environments where front end proxies may talk to both h1 and h2 applications.

Reply on news.ycombinator.com