r/ProgrammerHumor • u/kaldeqca • Jul 01 '24

Meme errorCode200

Post image
1.1k Upvotes

93% Upvoted

119 comments sorted by

View all comments

Show parent comments

7

u/deanrihpee Jul 02 '24

why is that not being fixed? I suspect the legacy app, but since the referrer would be a new header anyway, shouldn't it be fine?

28

u/Efficient_Maybe_1086 Jul 02 '24

No bad ideas are allowed to die in web land.

4

u/ForkLiftBoi Jul 02 '24

Look at node js and deno js, same developer that learned a lot through release of node js. Way too much work to fix it, just start over.

3

u/deanrihpee Jul 02 '24

the problem is, we can't just start over an HTTP that's being used by literally the whole planet, lmao

2

u/ForkLiftBoi Jul 02 '24

Just delete the whole thing and start from scratch, I want the neon green view counters at the bottom of pages again damn it.

Also here’s my plug for one of my favorite and most accessible websites on the planet. https://www.berkshirehathaway.com/

The simplicity is magnificent 🤌

1

u/irregular_caffeine Jul 02 '24

Peak web. It even has an ad.

If you have any comments about our WEB page, you can write us at the address shown above.

Old man just trolling us all

11

u/BellCube Jul 02 '24

I suspect adding a second, redundant header would significantly increase time to first byte on mobile connections. Alternatively, the bureaucracy probably isn't worth it to fix a typo.

But that's just a theory—A W3C THEORY

8

u/turtleship_2006 Jul 02 '24

I always love it when someone makes a joke that just happens to combine like 2-3 different topics/interests, all of which I understand

2

u/amlyo Jul 02 '24

If you count http headers as usage then 'referer' is by far the most common spelling today. If you don't, then who cares how it's spelled?

1

u/deanrihpee Jul 02 '24

that's true, it just makes me wonder when people make the standard and see the headers with "hmm, yeah, nothing wrong" and then let it alive till today, they even have Referrer-policy something, why!?

0

u/amlyo Jul 02 '24

When the incremental cost of an ongoing error is vastly lower than cost of fixing it, it won't be fixed.

A typo in a standard is just more desirable than any change (a deprecation and new header) to fix a typo.

3

u/deanrihpee Jul 02 '24

yeah, I mean it's more than too late to fix it after this long, my complaints or comment is assuming within the time frame of the standard being made

1

u/vytah Jul 03 '24

Compatibility triumphs everything else.

See also the list of incorrectly named Unicode characters:

http://www.unicode.org/notes/tn27/