Although I agree with the implied sentiment that “the Perfect is the enemy of the Good Enough” (especially for low-profile personal web-presence) and that naval-gazing about protocols can become a counterproductive rabbit-hole, sometimes it can also be risky to oversimplify in the other direction without at least parenthesizing the caveats too. For example this “HTTP/1.1” site points out how desync attacks make HTTP/1.1 robustness a bit of a game of Whack-a-Mole. For certain sites (even some personal sites) this can occasionally matter.
atzanteol@sh.itjust.works 2 months ago
There is zero question about it. It will be absolutely fine for some dude’s static website over a residential internet connection.
undefined@lemmy.hogru.ch 2 months ago
atzanteol@sh.itjust.works 2 months ago
Same? HTTP/1.1 ran the entire internet for 20 years and is still the majority protocol. It’s fine for a personal website.
rowanthorpe@lemmy.ml 2 months ago
Although I agree with the implied sentiment that “the Perfect is the enemy of the Good Enough” (especially for low-profile personal web-presence) and that naval-gazing about protocols can become a counterproductive rabbit-hole, sometimes it can also be risky to oversimplify in the other direction without at least parenthesizing the caveats too. For example this “HTTP/1.1” site points out how desync attacks make HTTP/1.1 robustness a bit of a game of Whack-a-Mole. For certain sites (even some personal sites) this can occasionally matter.
kernelle@lemmy.world 2 months ago
Obviously someone who has never actually tested 1.1 vs 2 vs 3 lmao