The creator of Sublime Text tends to go silent for long periods between stretches of activity, which always makes me wonder about the future of the project. It's a shame, since ST is a well-thought-out editor with great attention to detail, and of course the speed argument (compared to Atom and VS Code), while beaten to death, still holds true. Of course, it's up to the author himself to choose how he communicates, m…
I also consider the existence of http://docs.sublimetext.info a bad sign. The way I perceive this: At some point, an enthusiastic user was so fed up with the sub-par documentation that they decided to take matters into their own hands, and create a better documentation. But instead of working with the community, the Sublime project people/person just... did nothing? Was there any communication? I don't know. Why not provide the documentation on github and accept PRs? The Sublime project should push for docs.sublimetext.info to be merged into the official documentation.
Same with https://github.com/SublimeTextIssues/Core/issues. Why is the bug tracker "community run"? What does that even mean, considering the "community" can't fix any bugs? I absolutely cannot understand why the author of the software doesn't seem to participate at all in the bug tracker. Here's a quote from https://github.com/SublimeTextIssues/Core/issues/594 (from 2014, so I don't know whether it is still true) > Unfortunately, the only thing I can say is it'll get fixed if Jon Skinner sees it as a big enough priority. Our intent in creating this unofficial Issues page was to have a curated place where known issues can be collected together and triaged, and he can use it as he sees fit to fix bugs in upcoming releases. Without a more direct feedback mechanism, this is the best we can do, at the moment.
What I'd also like to see is a road map for the future with regular (2-4 weeks) status updates.