Ask HN: Why hasn't x86 caught up with Apple M series?
432 points by stephenheron 3d ago 616 comments
Ask HN: Best codebases to study to learn software design?
103 points by pixelworm 4d ago 90 comments
RFC 8594: The Sunset HTTP Header Field (2019)
28 aiven 10 8/28/2025, 7:35:22 PM datatracker.ietf.org ↗
The Sunset HTTP Header Field - https://news.ycombinator.com/item?id=19926775 - May 2019 (82 comments)
“Sunset” is marketing speak.
I understand that this functionality can be easily added as a plugin, but not everyone is aware that such a thing even exists. With default support, it will be easier to upgrade to new API versions and keep stuff up to date.
It explicitly doesn't have to mean deprecation, the standard says it could also be returned from any short-lived resource. There's no way to see if the header applies to the whole server or just the specific resource or even query parameters, and no way to deduplicate to ignore known warnings.
It's nice when tooling builds this sort of stuff in, because it also encourages APIs to implement it.
For example, if drag and drop and copy and paste didn't exist, it probably wouldn't be created today because you need 2 programs to agree on accepting the format (you can't even drag and drop from most software except file managers...). And even conventions that ALREADY exist are being forgotten with every year.