Live data from Hacker News

Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

news.ycombinator.com

11–20 of 69 posts

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#11
post #4

Yay! Nothing better than to put something that screams "bleeding edge" to handle all your traffic. YOLO, amirite? update: I love the unexplained downvotes, can't help but feel that as there's no argument they can make against what I wrote they are implicitly acknowledging that the point I made is, as it happens, correct.

I'll explain it, if you'd like.

Correct, no one is making an argument against what you said, because everyone understands that point. For most people, it doesn't need to be said. No one is ripping out production infrastructure and replacing it with this image. There's no comment anywhere suggesting it.

What you're doing is called "preaching to the choir". You're trying to be a contrarian to show everyone how smart and mature you are. Yolo, amirite? But not you! You're thoughtful and have experience and know not to do this! You're still running Debian Stable!

But really, this is just a cool Show HN project, posted on a Sunday night, and no one cares about your thoughts on the risk of bleeding edge. So they downvote and move on.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#12
post #11
post #4

Yay! Nothing better than to put something that screams "bleeding edge" to handle all your traffic. YOLO, amirite? update: I love the unexplained downvotes, can't help but feel that as there's no argument they can make against what I wrote they are implicitly acknowledging that the point I made is, as it happens, correct.

I'll explain it, if you'd like. Correct, no one is making an argument against what you said, because everyone understands that point. For most people, it doesn't need to be said. No one is ripping out production infrastructure and replacing it with this image. There's no comment anywhere suggesting it. What you're doing is called "preaching to the choir". You're trying to be a contrarian to show everyone how smart an…

Thanks for the labels. Appreciated how you put me in my rightful place.

Sorry if I'm being such a joy killer. I guess I've been witness to too many failures for not feeling to call this out before someone gets burned.

Oh right, but no one needs to be told to be careful, right... No one is here to learn anything, as we all already know everything. Makes you wonder what's the point of showing something new in the first place.

And please spare me the "no-one suggested to replace prod infra with this". Does the readme say anywhere "experimental, not for prod use"?

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#13
post #2

Looks I don't need Cloudflare anymore XD.

Yes, it's "almost" comical. The advantage of having a CDN with a pop in every city, vs. just having 3 or 4 well placed POP's around the world will be marginal once HTTP3 is broadly supported.

Aside from lowering latency, a big "edge footprint" also naturally load-balances and allows for more specialized localization, from what I can think of off the top of my head. I don't have much practical experience here so correct me if my speculation is off, anyone.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#16
post #4

Yay! Nothing better than to put something that screams "bleeding edge" to handle all your traffic. YOLO, amirite? update: I love the unexplained downvotes, can't help but feel that as there's no argument they can make against what I wrote they are implicitly acknowledging that the point I made is, as it happens, correct.

Because no one is suggesting you use this to "handle all your traffic" anywhere.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#17
post #4

Yay! Nothing better than to put something that screams "bleeding edge" to handle all your traffic. YOLO, amirite? update: I love the unexplained downvotes, can't help but feel that as there's no argument they can make against what I wrote they are implicitly acknowledging that the point I made is, as it happens, correct.

Because no one is suggesting you use this to "handle all your traffic" anywhere.

Neither is the contrary suggested. I wouldn't point out something marked as experimental/not for prod use.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#19
post #18

I'm just curious, is there a reason not to use a multi-stage docker build here? There are a ton of build steps, and it seems pretty tedious to have to start from scratch every time while developing the image without any layer caching.

Hi, my main task this weekend was to get it fully working. I will break down the steps over this week to utilize cache layers. I will try to get it done hopefully this week or by the weekend depending on work. Thanks a lot for your feedback.

Re: Show HN: Nginx Image with HTTP/3 (QUIC), TLS1.3 with 0-RTT, Brotli

#20
post #17

Earlier quoted context omitted.

Because no one is suggesting you use this to "handle all your traffic" anywhere.

Neither is the contrary suggested. I wouldn't point out something marked as experimental/not for prod use.

They literally say

> All built on the bleeding edge. Built on the edge, for the edge.

The only suggestion that this is meant "to handle all your traffic" is from you.

It seems like your main complaint is that the author didn't use some specific 'experimental/not for prod use' tag. For my mind, that's exactly what 'bleeding edge' implies, but if you think it doesn't why not simply suggest that they add such a tag? No charitable reading of the post suggests malicious or careless misleading.

Post reply on HN