I still think that it's educational malpractice to assume nontrivial working knowledge of a different, unrelated* field without highlighting that assumption for the reader.
(* "unrelated": yes, Haskell is "math-y," but category theory and linear algebra are not closely related.)
On Haskell in general? In theory I like the concision and abstraction-friendliness it enables, but its affordances for prying open those abstractions and observing how data flows through a system are pretty bad. I think if it were more tooling-friendly, and if that tooling provided strong observability, I would like it a lot; but as is, I'd rather program in languages that optimize for faster programmer feedback loops.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm curious what your current thoughts are on this experience in particular and Haskell in general.
I still think that it's educational malpractice to assume nontrivial working knowledge of a different, unrelated* field without highlighting that assumption for the reader.
(* "unrelated": yes, Haskell is "math-y," but category theory and linear algebra are not closely related.)
On Haskell in general? In theory I like the concision and abstraction-friendliness it enables, but its affordances for prying open those abstractions and observing how data flows through a system are pretty bad. I think if it were more tooling-friendly, and if that tooling provided strong observability, I would like it a lot; but as is, I'd rather program in languages that optimize for faster programmer feedback loops.