If you have a personal problem with @jdegoes, then damn well take ownership of your inability to work with a difficult person, rather than laying it at the door of unknown, unnamed hypothetical contributors. /12
-
-
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. /23Show this thread -
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. /24Show this thread
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
This Tweet is unavailable.
- Show replies
-
-
-
It sounds like you're bumping up against sunk cost fallacy. The real question to ask yourself is what does a continued investment in Scala yield, and does this future investment of your time in Scala outperform other options (Rust, Go, Java, etc). Only you can answer this.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I'm really sorry to hear that. Some folks in my network that had left the community have been talking about coming back to Scala, so I've been pretty excited. I didn't stop to consider that not sheltering bad actors would also worry folks w ties to or vested interests in them
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.