3 ms·
Well I would consider this a bit of a harsh take on Haskell programmers and not really a true statement, either. I don't think it's particularly offensive that
by klodolph 8y ago
Well I would consider this a bit of a harsh take on Haskell programmers and not really a true statement, either.
I don't think it's particularly offensive that some communities have developed alternative terminology for the same concepts. For example, whether you call something a "hash", a "map", or a "dictionary" is not especially consistent. Haskell programmers spend a large amount of time talking about type systems, mostly because Haskell has a large and complicated type system which is constantly evolving, so I would expect people who use Haskell to have some differences in the way they talk about type systems.
The whole typed programming research crowd is basically doing research into how you can prove at compile time that certain properties of a program will hold at runtime. To them, that's what a "type system" is. I wouldn't say that Haskell programmers or programming research people are unaware of the terminology differences... I personally know some people who are programming language / type theory PhDs or professors, and they're usually more excited to tell you about something they added to GHC or something they did with Agda or Coq, and less excited about dissing JavaScript.
- tom_mellior 8y ago> Well I would consider this a bit of a harsh take on Haskell programmers and not really a true statement, either. I did write "subsets", not "all Haskell programmers". > I personally know some people who are programming language / type theory PhDs or professors Me too, hence my statement above.