←back to thread

Go-Safeweb

(github.com)
188 points jcbhmr | 2 comments | 14 Nov 24 03:04 UTC | HN request time: 0.422s | source
Show context
nox101 ◴[14 Nov 24 05:22 UTC] No.42133345[source]▶
What does this mean?

> NG1: Safe API Completeness > Creating safe APIs for all the corner cases might result in a bloated codebased. Our experience shows that this isn’t necessary.

To me "Safe API" means it's hard to use the API incorrectly. I see lots of poorly designed APIs where it's easy to use the API incorrectly and then you don't know you've used it incorrectly until (1) the edge case you weren't aware of appears (2) you get pwnd by an exploit because you used it wrong.

replies(1): >>42133619 #
1. ongy ◴[14 Nov 24 06:29 UTC] No.42133619[source]▶
My reading is that it's supposed to provide an API that's safe to use, but might not allow to do everything technically possible within the HTTP spec.
replies(1): >>42136085 #
2. kele ◴[14 Nov 24 13:45 UTC] No.42136085[source]▶
That was the intention of that paragraph.