I know there was some drama in the Scalaz / typelevel thing, and that the typelevel coc was one of the outcomes, to help avoid such issues becoming such a problem. @dibblego maybe you can provide some perspective?
-
This Tweet is unavailable.
-
-
Replying to @eliaskjordan
Twitter is not an appropriate forum to detail this saga, even if you leave out the bias. You simply won't get an accurate description. That's just one exceptionally good example that flies in the face of any claims to "help." Even the quality of the code alone speaks to this.
1 reply 0 retweets 0 likes -
Replying to @dibblego
Fair enough, since I don’t know what happened. I do know there was no code of conduct at the time, could the existence of such a document helped deescalate the issue?
1 reply 0 retweets 0 likes -
Replying to @eliaskjordan
Yes there was a "code of conduct" at the time. It just wasn't entirely fucking ridiculous, and we happened to not call it that. No, the existence of a document does not help deescalate anything. The situation was deescalated by other means, limiting the inevitable destruction.
1 reply 0 retweets 0 likes -
Replying to @dibblego
Hmmm... ok. Would be intersted in knowing what actually happened. There is a major rift in the FP+scala community to this day. And it seems to be a result of the Scalaz/typelevel debacle. But, no one will speak of what actually happened.
2 replies 0 retweets 0 likes
The short of it is, some politicians insisted that I be forced, and the Scalaz project in general, to play a stupid fucking game. So I did. And then they lost that very game. And now they are pissed. Everyone[^1] has since left Scala behind. It's a waste of time. [^1]: todo
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.