I wrote an article about the history of the HTTP status code and what I think it tells us about designing specifications and APIs:
If you liked my @365-rfcs project, this is a direct outgrowth of that work.
I included a digression on the concept of historical contingency that got edited down significantly. It probably helped the article read better but I wish I'd figured out a way to talk about that more.
@darius this is great, thank you for writing and sharing. I appreciate the breakdown of the history, which was very easy to follow (as a semi-laypersonnin this area)
@darius @365-rfcs Thank you for sharing this. I'm curious how many opportunities are there today to actually invent something new, technology-wise. It seems most things are more like refinements and improvements of things that already exist(ed), or ports / reimplementations of existing techology between programming languages. On the other hand, there are still an infinity of problems to solve (often created by the technology itself), but they are rarely as signnificant.
@setthemfree Generally speaking if I could wave a magic wand and cause say 90% of people who do computer programming to magically know some other form of engineering instead I think it would be a better application of human minds, since I think there are more genuinely interesting unsolved problems in, say, environmental or power or civil engineering
Hometown is adapted from Mastodon, a decentralized social network with no ads, no corporate surveillance, and ethical design.