I belive that abstraction can be a double edged sword.
Pro. you write less code
Pro. Your code is easier to read for everyone familiar with the abstraction.
Con. You need a math degree.
Con. Harder to get contributors.
etc...
Tangentially. The docs also say that:
"In practice, cofree comonads are quite useful for annotating syntax trees, or talking about streams."
Sometimes you can learn the abstraction and one of its particualr use cases. And apply it when you find it, without needing the degree.
Also to answer your question:
"So I take it you believe that a degree in category theory is the bare minimum for people to expect to be able to understand other people's code?"
No, I don't believe so.
But the experiment of forming a team of people that knows all this to see how productive they are, would be nice to see.
Pro. you write less code Pro. Your code is easier to read for everyone familiar with the abstraction. Con. You need a math degree. Con. Harder to get contributors. etc...
Tangentially. The docs also say that:
"In practice, cofree comonads are quite useful for annotating syntax trees, or talking about streams."
Sometimes you can learn the abstraction and one of its particualr use cases. And apply it when you find it, without needing the degree.
Also to answer your question: "So I take it you believe that a degree in category theory is the bare minimum for people to expect to be able to understand other people's code?"
No, I don't believe so.
But the experiment of forming a team of people that knows all this to see how productive they are, would be nice to see.