Kind of a hard thing to share because I don't like to speak negatively about things but there's something concerning that I am noticing. The @typescript team has never beed exceptionally receptive of community PRs but usually after some time and some push they get around things
Since the Go port was announced I've noticed even more reluctance to accepting PRs, many times you can't even get a review. And folks are demotivated. For example @AndaristRake has worked on https://github.com/microsoft/T... and on many other PRs that can improve the Effect ecosystem
@AndaristRake And nothing seems to be moving. I don't quite know the way forward, what can we do to improve TS? I don't really want to think our only option is to fork and maintain a parallel compiler that has more fixes but as of today I can't see any other solution.
@AndaristRake We've been there already with forking TS for TS+ and I know it's not an impossible task, and this time it will only include fixes that are already PR'd upstream. But I don't want to divide, I'd really like to work together instead.
Also I'd like to thank the TS team, while we have some concerns they've built something exceptional! This is meant to make it better.