Second time I run into a developer on itch.io who doesn't know what a #web server is and thinks they need to code a #NodeJS app to serve static files.
This is terrifying. It's the future Google wants to build, with their HTTP 2.0 and Wasm: a future when even the basics are horribly hard and not even developers know how the web works because it's all a black box.
I'm begging you: fight this. Educate people. Don't let openness die.
@notimetoplay So-called "HTTP 2" is /not HTTP/ and I will die on this hill!!
@silverwizard @IceWolf That was no typo. HTTP 2 is binary. It can no longer be used in trivial ways.
@silverwizard @IceWolf Sure, if you're a pro web developer with the time and energy to dig. If it was like that in 1999, Google wouldn't exist. This is called "pulling the ladder up after you got on top".
@notimetoplay @silverwizard @IceWolf i mean, just import libcurl. you don't implement tcp yourself so i don't see using a HTTP library that will likely be 100x better than whatever you will write isn't too offensive
@tay @notimetoplay @silverwizard You're missing the point.
The point is that with text protocols, you don't HAVE to use a thing somebody else already wrote.
And besides, someone had to write libcurl in the first place.
Binary just makes shit difficult for literally no reason.
@IceWolf @notimetoplay @silverwizard yes. someone who can dedicate a lot of time can do the work of writing a good HTTP client.
H2/3 are remarkably faster than H1
@tay @notimetoplay @silverwizard "Faster"? Meh. Not by any metric that matters.
Plain text worked in 1990 and it still works now.
@tay @notimetoplay @silverwizard If you want to make your site faster, don't rewrite fucking HTTP, just use less ads and random cruft.
@IceWolf @notimetoplay @silverwizard well we both know that's not happening, and H2 already exists, so why not use it. Not like H1 is going anywhere anyway 🤷
@tay @notimetoplay @silverwizard For NOW.
What d'you think Google's plan is? Real HTTP is probably going to get "deprecated" once "everyone's on things that support HTTP 2 anyway".
@IceWolf @notimetoplay @silverwizard ???????????????
You are aware the internet is decentralised? Like, Google doesn't run the entire internet. The current version for the H2 spec wasnt even authored by anyone at Google. It was Mozilla & Apple.
@tay @IceWolf @silverwizard Yes, that's what bothers them, so they're trying to snuff out all that openness.
@notimetoplay @IceWolf @silverwizard i literally have RFC 9113 open on the computer in front of me it's hardly closed
@tay @notimetoplay @silverwizard "publicly viewable" and "actually open to community involvement" are two different things. (Exhibit A: Android. Exhibit B: Chrome.)
@tay @IceWolf @silverwizard You... realize big tech is on all the standards committees, and effectively controls them, right?
@IceWolf @notimetoplay @silverwizard again. RFC 9113 is attributed to people from Mozilla and Apple. Not Google. It is owned by the IETF, who again, is not Google.
Google does a lot of bad shit - yes, but this isn't even something to blame on them, even if H2 was a bad thing, which it's not.