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

I've read your points several times and I still don't get who this message is addressed to? You must know full well that once bad blood sets in, calls for unity will do nothing to make people feel better or to change people's behavior or ability to collaborate in the future.

I'm just venting my frustration. I have a strong faith in people being able to resolve differences with time and I think there's plenty of evidence they can. Three years ago, disagreements between @milessabin and @odersky made @dickwall leave Scala. Now they're working together.

So now you're dragging everybody in too?