Live data from Hacker News

How to build an absurdly backwards-compatible website

flower.codes

41–50 of 67 posts

Re: How to build an absurdly backwards-compatible website

#41

> Let's face it: the internet is broken. This is where I disconnect. The internet is not broken. Maybe arguably the _web_ is broken, and specifically, web pages are broken (the HTTP protocol is still a wonderful thing). I wish technical authors would stop making the internet-is-broken meme when they really mean the web is broken. Sure, there's plenty broken with the internet in other ways (DNS, encryption, government…

[deleted]

Re: How to build an absurdly backwards-compatible website

#42
This is great. I'm not a front-end dev but I have a low-traffic personal site where I like to experiment. One of my hobbies is to find out how small, lean and compatible with old browsers I can make it, while still looking modern-ish (very subjective I know) and with _some_ interactivity that can degrade gracefully.

So far it's pretty much usable in IE6 and Mosaic 2 (1993).

Re: How to build an absurdly backwards-compatible website

#43
post #36

Earlier quoted context omitted.

"The internet is broken" he says; a moment later he greets his wife he met on tinder, then he opens a 3blue1brown video, a YouTube channel that he himself admits is the first teacher in his life that made math truly click in his brain, in the room right after his son is playing Minecraft with his best friend, a little girl from Japan who he has never met but already knows a bit of japanese thanks to their long chats…

>wife he met on tinder I chuckled on that part

It happens a lot: https://www.businessinsider.com/tinder-married-met-husband-o...

Re: How to build an absurdly backwards-compatible website

#44

> Let's face it: the internet is broken. This is where I disconnect. The internet is not broken. Maybe arguably the _web_ is broken, and specifically, web pages are broken (the HTTP protocol is still a wonderful thing). I wish technical authors would stop making the internet-is-broken meme when they really mean the web is broken. Sure, there's plenty broken with the internet in other ways (DNS, encryption, government…

>The internet is not broken.

With BGP it's just about limping along with trust

https://www.bleepingcomputer.com/news/security/major-bgp-lea...

Re: How to build an absurdly backwards-compatible website

#46
> I use the Caddy webserver

I used to love Caddy. Not so after the move to 2.0 when they got the json formatted config thing going on. Of course there is still Caddyfile but most of the time I'm bashing my head on their json focused documentation page to find out how can I do that same thing from a config file. I'm pretty sure there might be somewhere but I don't want to read a book I just need a nice quick web server that runs from a single binary like v1 did.

Re: How to build an absurdly backwards-compatible website

#47

> Let's face it: the internet is broken. Again and again: It's not the internet broken, its only HTML plus the required interplay of a bazillion of specs.

For most people, that's 99% of "the internet".

Almost all "other" protocols, have been replaced by HTML over HTTP. (from chat applications, web interfaces for mail, forums instead of newsgroups, etc.)

Re: How to build an absurdly backwards-compatible website

#48

> Let's face it: the internet is broken. This is where I disconnect. The internet is not broken. Maybe arguably the _web_ is broken, and specifically, web pages are broken (the HTTP protocol is still a wonderful thing). I wish technical authors would stop making the internet-is-broken meme when they really mean the web is broken. Sure, there's plenty broken with the internet in other ways (DNS, encryption, government…

> The internet is not broken.

> (the HTTP protocol is still a wonderful thing).

But almost all websites are requiring an HTTPS and you know what? I have a dozen of dumbphones who can not access webpages because HTTPS is no longer supported by vendor of device or absolutely can not access https because handshake process takes too long time for gprs (if no edge). If HTTP is so wonderful than why I can not use it without all the stupid security?

Re: How to build an absurdly backwards-compatible website

#49

Earlier quoted context omitted.

Oooo I like this! I’ll have to steal it. Thanks for the tip!

Don’t do this. What if something strips the header between the client and your server? Always upgrade to HTTPS. Not doing so isn’t worth supporting 25 year old browsers

No post body was provided.

Re: How to build an absurdly backwards-compatible website

#50
post #48

> Let's face it: the internet is broken. This is where I disconnect. The internet is not broken. Maybe arguably the _web_ is broken, and specifically, web pages are broken (the HTTP protocol is still a wonderful thing). I wish technical authors would stop making the internet-is-broken meme when they really mean the web is broken. Sure, there's plenty broken with the internet in other ways (DNS, encryption, government…

> The internet is not broken. > (the HTTP protocol is still a wonderful thing). But almost all websites are requiring an HTTPS and you know what? I have a dozen of dumbphones who can not access webpages because HTTPS is no longer supported by vendor of device or absolutely can not access https because handshake process takes too long time for gprs (if no edge). If HTTP is so wonderful than why I can not use it withou…

That's like saying why can't I use HTTP without packet reliability from TCP or QUIC. Packet reliability, or security in your case, happens on a lower network layer. Just because HTTP lacks packet reliability, that doesn't mean that it now sucks.
Post reply on HN