41–50 of 91 posts
I think this is a good change because GOAWAY is simpler, more obvious, and has a tone matching the actual operation. Plus, the har-har pretense that GTFO means "General termination of future operations" is childish. With that out of the way, the pearl-clutching about the word "fuck" and how unprofessional it is irritates me. We have this weird notion that it's OK for us to curse individually but that there's this wid…
I personally am a fan of professional tools breaking away from the need to be serious all the time. It is just that I experience joy when I find little things like GTFO in the world which not only make sense in their context but have a bit of humor. So I guess I just disagree with the idea that standards should not contain anything crass. Also I have a question concerning the 4th point as I am admittedly unfamiliar w…
I believe that the surprise would come from it not meaning "get the f* out." Which makes perfect sense to me - GTFO has a meaning, and re-backronyming it can only harm understanding of the standard. Also consider non-native English speakers, which is really important when developing international standards. The fact that someone suggested a corresponding "HTTP TITS" should set off at least minor warning bells that "H…
Edit: To further clarify I mean surprise about what it stands for when both interpretations convey a similar idea.
Dennis Ritchie: “So fsck was originally called something else” Question: “What was it called?” Dennis Ritchie: "Well, the second letter was different"
I personally am a fan of professional tools breaking away from the need to be serious all the time. It is just that I experience joy when I find little things like GTFO in the world which not only make sense in their context but have a bit of humor. So I guess I just disagree with the idea that standards should not contain anything crass. Also I have a question concerning the 4th point as I am admittedly unfamiliar w…
I believe that the surprise would come from it not meaning "get the f* out." Which makes perfect sense to me - GTFO has a meaning, and re-backronyming it can only harm understanding of the standard. Also consider non-native English speakers, which is really important when developing international standards. The fact that someone suggested a corresponding "HTTP TITS" should set off at least minor warning bells that "H…
Earlier quoted context omitted.
Professionalism is much more than competence and/or skill, just like good sports is about good sportsmanship too.
Perhaps it would be better for everybody if "professionalism" focused more on competence and skill, and less on politically-correct bullshit.
(I really wanted to close with a saying along the lines of "one man's politically-correct bullshit is another person's basic standard of human decency", but I saw somebody say this - or something very much like it - once on HN, and it was followed up by a comment from somebody complaining that this level of politically-correct nonsense was infringing on his fundamental immutable human right not to be implicitly compared to something inhuman. Which I suppose is fair enough. And I certainly wouldn't want anybody to feel oppressed.)
I think this is a good change because GOAWAY is simpler, more obvious, and has a tone matching the actual operation. Plus, the har-har pretense that GTFO means "General termination of future operations" is childish. With that out of the way, the pearl-clutching about the word "fuck" and how unprofessional it is irritates me. We have this weird notion that it's OK for us to curse individually but that there's this wid…
I personally am a fan of professional tools breaking away from the need to be serious all the time. It is just that I experience joy when I find little things like GTFO in the world which not only make sense in their context but have a bit of humor. So I guess I just disagree with the idea that standards should not contain anything crass. Also I have a question concerning the 4th point as I am admittedly unfamiliar w…
I believe that the surprise would come from it not meaning "get the f* out." Which makes perfect sense to me - GTFO has a meaning, and re-backronyming it can only harm understanding of the standard. Also consider non-native English speakers, which is really important when developing international standards. The fact that someone suggested a corresponding "HTTP TITS" should set off at least minor warning bells that "H…
Considering the general highlevel meaning of "get the fuck out" and "General Termination of Future Operations" in the context of this protocol is the same, is it really going to harm anybodies understanding of the standard? Worse case scenario, people know what it does, but are surprised that it is an acronym for something "SFW".
> Also consider non-native English speakers, which is really important when developing international standards.
Is the concern here that they will not be familiar with the typical "internet meaning" of GTFO? They might not get the joke, but I don't see how that would harm their understanding of the standard. They'll read about GTFO, learn that it means "General Termination of Future Operations", learn what that means, and they'll be good to go. Just because they don't get a chuckle out of it doesn't mean that their ability to work with it is impeded.
There's a lot of stuff out there by comedians about how saying "fuck" is probably the cheapest way to get laughs. It's pretty much cheating. At least saying your server is a teapot is slightly unexpected.
considering what the output is supposed to be, I would think something like PLZSTOP would be slightly better than GOAWAY, but in any case GTFO is not even really funny, kinda wears away at our already limited supply of swear words, and isn't worthy of the high-grade humor that is internet specification humor.