Jon Pretty

As I already said, my entire career has been based around Scala. If the actions of @typelevel and @skillsmatter are making *me* reconsider that choice, then how do they look to a developer who hasn't invested nearly so much of their life into this language? /22

But the actions are unlikely to be reversed. @typelevel will inevitably continue to do a lot of good work for the community, and I shall continue to support their positive contributions, though they shall be forever tainted by yesterday's self-indulgent decision. /23

I can do no better than suggest that the best we can do is to move on quickly and hope, against expectation, that @typelevel and @jdegoes can coexist in the same community, and find the magnanimity not to tear it apart. /24

They weren't considered relevant in the @typelevel decision, so I didn't address them here, but the keynote I gave at @lambda_conf this year loosely covered my thoughts around the issues @travisbrown raises.

Your thread repeatedly attacks Skills Matter, whose decision had nothing to do with Typelevel’s, and was a direct response to the kinds of behavior described in the post.

It’s really hard to take your response to @AgnieszkaBratek as written in good faith. You attack SM in this thread for a decision that had nothing to do with TL, but you didn’t address the reasons for that decision here because they weren’t relevant to TL’s?

I was trying to answer her as best I could. My thread focused much more on @typelevel than @skillsmatter, as the latter is a commercial organisation, and because I had never previously addressed the issues Typelevel raised. SkillsMatter came first because it happened first.