135 karma · joined January 1, 2021
Please do not be disrespectful toward others.
Separate the commenter from the comment.
Smart commenters still make dumb comments now and then. And vice versa.
Consequently, the "identity" of the commenter is not a reliable predictor of the quality of the comment.
Shared accounts such as this one can address this problem.
Each comment must stand on its own, apart from identity and historical karma.
Perversely, you are doing exactly the thing that the statement "Consider this: I have a high emotional IQ" is exhorting you not to do, which is to tunnel vision your way to one of the possible outcomes--the one where it isn't true--and then try to reflexively use it to justify the starting position that leads to that outcome. You are failing to consider the counterfactual.
I know. I said it. Why am I having to repeat this?
> what part of your description was condescending
What? I'm not saying my description was condescending. It is a description of your reply. It pinpoints what was condescending about that reply. You are "leaping at the opportunity" to explain "how to human". This is condescending. It would be like if I launched into an explanation about why it's a good idea to shower and maintain good hygiene, as if you needed to be told that body odor can be unpleasant for other people and might make them not want to be around you.
1. Do you think that your comment https://news.ycombinator.com/item?id=26628064 is nice or shows "respect for others' humanity"?
2. What about your message, or any of the other messages here, exempt them from requiring the sorts of obligatory pleasantries ("good morning"; politeness and courtesy that should be "[written] in words"; etc) that you're so strenuously arguing for as a "baseline expectation"?
(I'm going to pre-emptively call bullshit on any "giving a taste of one's own medicine" response to the latter question. I'm not interested in dishonest answers.)
You're responding to an anonymous comment on a message board with zero IRL context. Consider your own ability to diagnose here.
"You can write a compiler in a weakly typed language that resembles a compiler in a strongly typed language." Happy now?
The point, which you have ignored, is that there are strongly typed languages where the features you're relying on are not present. In fact, this is true of a bunch of the compilers that are among the most widely used in the world--ones that people are using to build projects written in C and C++ and things like the language support baked into IDEs for Java, C#, etc. So the relevant factor is not "strong vs. weak?" but rather those features (structural matching, etc) that you are relying on.
And let's be real, the original comment ("I'd rather put my hand in boiling water than develop a compiler in a dynamic weak typed language"; now flagged) was no more than a drive-by insult.
Consider this: I have a high emotional IQ and acutely understand whatever lesson you think you're imparting here, I just don't have the kind of bullshit budget required in this context.
Here's the obvious consequence that no one ever seems to get, even with having it explained to them: if I'm going to have to start dropping things on the floor and make some people unhappy, guess who I'm going to choose to be the recipient? All the people most responsible for squandering the resources that were available.
Being delayed by a "good morning" from an oblivious coworker? More than just annoying. (Obligatory "pleasantries" from coworkers who otherwise take glee in making you miserable and obstruct you for sport? Much, much worse.) We're not friends--we're coworkers, at least nominally, and I probably have a stack of shit this high to deal with--that you may or may not be the cause of. How about this for being "nice": don't force me into dealing with your bullshit, against my wishes. Where's your recognition that I'm a human with feelings and needs?
I don't want that kind of stuff in bug reports for the same reason that I don't want to have to deal with "hello", "good morning", from coworkers in messenger applications, and I will assume that for your sake you don't want to deal with it either, unless you explicitly say so.
So if this is a requirement for writing and responding to bugs, then you should "say it in words" that that's what you want.
> language that's already ~30 years old by now
Relevance?
> If someone interested in a compiler doesn't download it, it's not a excuse, it's a filter. Or a warning sign.
You're so invested in gatekeeping that you're confusing the point of research with technofetishism.
Here's what Joe Armstrong had to say in "The Mess We're In":
"I downloaded this program, and I followed the instructions, and it said I didn't have grunt installed! [...Then] I installed grunt, and it said grunt was installed, and then I ran the script that was gonna make my slides... and it said 'Unable to find local grunt'."
Looks like someone needs to go dig up Joe and let him know that the real problem is that there was a mistake in letting him get past the point where he was supposed to be filtered out.
No? That's a pretty good description of the sort of metaprogramming that Lisp gives you, and Lispers are really enthusiastic about that kind of thing. People will dispute the parallels, but the real difference comes down to:
- non-Lisp languages being significantly less powerful
- Lisp's veneer of respectability
... which shouldn't be all that odd, considering the person who gave us "design patterns" was Dick Gabriel, a Lisper.
At least the "SingletonFactoryWorkerVisitor" programmers use a nomenclature that reflects the ontology the object is supposed to fit into.
The buzzword of 2020/2021 appears to be "grifter" and its variations.
On topic with the article and related to this is the word "dogwhistle". (The funny thing is that "dogwhistle" can itself be a dogwhistle.) It doesn't get used as much in my experience as "grifter", though, which is so wantonly thrown about nowadays that it may as well have no meaning.
I avoid using both of these words. There are better ways to say it.
The people who live on GitHub are unfortunately unable to recognize any distinction.