6 ms·
He was at the premiere computer science research organization for decades. And you presume that he's not familiar with sum types, because if he was, he would h
by AnimalMuppet 7y ago
He was at the premiere computer science research organization for decades. And you presume that he's not familiar with sum types, because if he was, he would have included it, and therefore he can't have been familiar with it, because he didn't include it? That's the most amazingly arrogant thing I've heard in a while.
The fact is that Rob almost certainly knows more than you, rather than less. And he still made the choices he made. That should make you ask questions, not about Rob's knowledge, but about yours.
- crimsonalucard 7y agoHe certainly does know more than me and is more successful than me and is smarter than me. But there are many areas of research in computer science. I'm saying Rob Pike is likely not to have been familiar with sum types and type theory in general (which is more Math then computer science). The design of his language looks that way. Someone knowing much more or having clearly a higher rank does not mean they know everything. And there are certainly things that you, I or Rob Pike doesn't know. Idolization of people and assumptions based off of reputation are highly biased and unrealistic. Counter my arguments with logic and evidence. Stuff like this person is "better than you" therefore you must be wrong is weak. Never have I ever directed a direct insulting statement AT someone on HN. You literally called me ARROGANT. Do not insult me. This is a place where we discuss things not a place where we insult people. I will have no further discussion with someone who directly and explicitly insults me. Don't bother responding, I will not discuss anything with someone who cannot be civil.
- thatswrong0 7y agoThis feels like the opposite of an ad hominem fallacy
- AnimalMuppet 7y agoWell... those Bell Labs types were polyglots. They tried a lot of things in a lot of languages. Does that mean that Rob Pike knew about sum types? Not necessarily, no. But it gives you two possibilities. 1. Rob Pike spent all that time at Bell Labs, with all these CS experts, read and wrote all those papers, and never heard about sum types. That's... possible. It's not the way I would bet, but it's possible. 2. Rob Pike knew perfectly well what sum types were, and left them out of Go, because he thought they didn't fit with what he was trying to do. To me, the second is both more charitable, and more in line with what I think Rob Pike's background and experience would have exposed him to. crimsonalucard obviously disagrees. He seems to think that sum types are so obviously the right thing that Pike could not have possibly not put them in Go had he known about them, and therefore he could not have known. And that is in fact possible. But it seems to me to better fit with Pike's background, as well as with the principle of charity, to assume that he knew. And still he chose to leave them out. Now, he could still be wrong. And we can discuss whether sum types are really a good fit for what Go is trying to do. But the assumption that he couldn't have known, or he would have done it the way someone else thinks he should have, is what grates on me. For what it's worth, the Go FAQ (at https://golang.org/doc/faq#variant_types https://golang.org/doc/faq#variant_types) says that they considered sum types, and didn't think they fit.
- crimsonalucard 7y ago> But the assumption that he couldn't have known Please read my initial assumption. In no place did I say he COULDN'T have known. Read it. I literally started the statement with "I think the designers probably didn't know" rather than "I know they COULDN'T have known." There is nothing to "grate" you here. I simply had an opinion and a guess, and you disagreed with it and decided to insult me. What grates me is the assumption that I said it's 100% true that Rob Pike didn't know what a sum type was. I think it's very likely he didn't know. If he did know then I am wrong. That's all. >For what it's worth, the Go FAQ (at https://golang.org/doc/faq#variant_types https://golang.org/doc/faq#variant_types) says that they considered sum types, and didn't think they fit. That FAQ should have been presented earlier in a cordial and civil way. If you did I would have admitted that my hypothesis was incorrect. Science logic and evidence rule the day and I try to not invest any emotion into any of my opinions. It's hard but I follow this rule. If the FAQ says he knows about it then he does and I am wrong. Instead you chose not to present this evidence and call me arrogant. There was no need to call me "Arrogant." It disgusts me to hear people talk like this. Either way the GO the language feels awkward in the way it uses product types and does indeed feel like Rob didn't know about them because the sum types certainly do feel more fitting then having a function return a tuple out of nowhere. I also disagree with the FAQ. Plenty of languages have constraint types that are placed on the subtypes of the sum type. There's no confusion imo. Also note that the previous sentence was just an opinion. Please don't call me arrogant because I have one.
- AnimalMuppet 7y agoWell, I didn't have the FAQ earlier. I was guessing then. And I don't see the FAQ as necessarily total vindication of my position. The language team considered sum types; it doesn't mean that Rob Pike did in the initial design. It could be that, after it was kind of mostly formed, they thought about sum types and couldn't find a sensible way to make them fit. Or it could mean that he considered them and rejected them from the beginning. The FAQ isn't specific enough to say. As for calling you arrogant: You are not the first person who has said, here on HN, that Pike "looked like he didn't know"/"must not have known"/"couldn't have known". Those conversations kind of run together in my mind. As a result, I was hard on you at least in part because others went too far. That's not fair to you, and I apologize. I also cannot call you arrogant for having an opinion. I also have one - you may have noticed this. ;-) However, I feel that I should say (and say as gently as I can) that you often sound very harsh on HN. A harsh tone causes many to read your content with less charity than the ideas might deserve. (I am not here trying to defend my interaction in this thread.) And this is not very helpful of me, because if you ask for advise on what, specifically, to change, I'm not sure I can give any. I mention it because you may be unaware of it, and awareness may help. I can easily see how the previous paragraph could offend you. I am not trying to do so. Forgive me if it causes offense.
- wwright 7y agoIt’s called “appeal to authority”: https://en.wikipedia.org/wiki/Argument_from_authority https://en.wikipedia.org/wiki/Argument_from_authority
- ses1984 7y agoThe name of this fallacy is appeal to authority.
- crimsonalucard 7y agohttps://news.ycombinator.com/item?id=6821389 https://news.ycombinator.com/item?id=6821389 Read that quote by Rob and the responses. IN the quote rob describes what he believes Generic Types are at face value... he literally takes it into a tirade about inheritance and hierarchies of classes... something that is not part of type theory at all. Honestly, it feels like he didn't know about Algebraic Data types. I'm not the only one who thinks this as shown from the responses to his quotation. One of the responses: "Or perhaps Rob Pike just hasn't explored the relevant literature in enough depth. At one point he admitted that he didn't know that structural typing had already been invented previously! This isn't to criticize Rob, I find his talks fascinating, I think he's awesome, he's a friend of my boss, etc. But he's hardly the first hard-core hacker to be ignorant of the degree to which type theory has seen dramatic advances since the 1980s."
- jeremyjh 7y agoHonestly this is really compelling evidence that Pike doesn't know much about type theory. That isn't terribly surprising, and the other early collaborators on the language that I know of also came from more of a systems background. I think its entirely likely that Go's crippled type system is partly an accident, and not entirely a design choice. It would be helpful if - with the benefit of hindsight - they would admit it, rather than invent post-hoc justifications for the way things are.
- jcora 7y agoI don't know man. I feel like there are places I know more than Rob Pike almost certainly. Like, I don't know, most of functional programming. I seriously doubt he knows what indexed monads are better than me. So, at the point they were creating Go, I think it's perfectly reasonable they had even less exposure to fp, and didn't actually know about these better solutions.