3 ms·
Seeing as the existing use is without the hyphen, shouldn't this proposal be updated to match?
by wizzwizz4 5y ago
Seeing as the existing use is without the hyphen, shouldn't this proposal be updated to match?
- dredmorbius 5y agoKen Thompson was once asked what he would do differently if he were redesigning the UNIX system. His reply: "I'd spell creat with an e." https://en.wikiquote.org/wiki/Ken_Thompson https://en.wikiquote.org/wiki/Ken_Thompson
- ctoth 5y agoHe finally did [0]! [0]: https://github.com/golang/go/commit/c90d392ce3d3203e0c32b3f98d1e68c4c2b4c49b https://github.com/golang/go/commit/c90d392ce3d3203e0c32b3f9...
- remram 5y agoThe biggest oops we're stuck with is the Referer HTTP header. At least that one was intentional.
- colejohnson66 5y agoIntentional? Really?
- saurik 5y agoI was confused by your comment, but I am betting you parsed "that one" as the referer situation; I am quite confident it referred to the creat situation.
- colejohnson66 5y agoYes. My understanding is that `creat` was intentional due to early limits on variable names `O_CREAT` is 8 characters (7 + null), but `Referer` was an accident. So parsing the parent comment as saying `Referer` was intentional confused me. “Why would you intentionally misspell that?”
- saurik 5y agoRight, but that was unlikely to be the correct parse as we don't normally use phrasing like that; we say "well, you might think X is Y, just let me tell you Z is actually way more Y... at least in your Z situation, A is true, which mitigates how Y it could be". There was a lot elided here, but the structure was the same.