Thoughts
It's just crazy to me the extent to which Sublime Text users want to pretend like everything is fine and dandy and there's nothing wrong
with the ecosystem. Like if you suggest using a LSP or tree-sitter they get super defensive and insist that the built-in packages are perfect. And then someone points a super obvious major bug in the default packages and they're like, 'Well um, that's a hard problem and you can't expect us to solve it.'
Developing a perfect syntax highlighting system for every programming language would be extremely hard for the Sublime staff to do. I don't know why they can't build LSP or tree-sitter into the editor and then use syntax definitions or language server implementations from VSCode or other editors.
But when I suggest that I got the replies:
> If you have specific dissatisfaction with a built-in syntax, file a bug on GitHub.
> All syntaxes written against latest ST syntax features, are (IMHO) quite complete and performant.
And I do have issues but my issues are the same issues that every one else is having. Like look at the number of referenced issues on this bug:
=> https://github.com/sublimehq/Packages/issues/2267
It breaks go-to-symbol; it's not a good bug.
Edit, the JS/TS syntax package volunteer maintainer on this issue:
> I think I've taken a couple of stabs at fixing it, but it turned into a huge pain (basically due to https://github.com/sublimehq/sublime_text/issues/3494, if I recall)
So there you have it, from the maintainer of one of the most complicated and most thorough default packages, Sublime's syntax highlighting system is inherently difficult to work with.