Jon Pretty

Scala is approaching an exciting but challenging period of change. We're about to get a whole host of new features which will enable us to write smarter, more elegant, more expressive code. We're at the forefront of technology, and it's going to be usable in Scala 3 soon. /20

And yet, after these two coincidental actions against @jdegoes in as many days, for the first time in over a decade, I have found myself considering whether I really want to be a part of this community. After the enjoyment of Scala World, it's sobering and even depressing. /21

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.