Recent searches
Search options
@bascule@mas.toHow to interpret RFC 2119 keywords:
- SHOULD: do this
- MAY: don't do this
- MUST: I'm going to open a can of whoop ass if you don't do this
@bascule * there is no actual can of whoop ass, I'm just saying that I would if I had one
@bascule No ‘shall’?
Why MAY is so negative? I think I saw it often used to indicate something that's a reasonable thing to do, but not something the RFC wanted to make a recommendation about either way (except to point out that the possibility exists and doesn't contravene any other requirements).
@robryk MAY is often used as a way to signal deprecations: things that can't be removed due to legacy interop reasons, but shouldn't be encouraged in modern implementations