Actually, it is more scalable and optimal to invest time implementing lsp and tree-sitteer building support because supporting more external packages and modes one by one for languages that maybe won't be popular after some years, so they will become unmaintained and unremovable from vanilla. Most of the code in the programming modes (and performance penalty) is actually dedicated to syntax highlight, indentation, and code navigation. Something that tree-sitee will do better and faster in most cases. Then language specific modes could add just some extra specific details... And we can invest then our time improving, not implementing basic support.
Some external packages are also very limited and there are other external additions and plugins to make them functional... So adding more and more modes for languages is worthless. Use a ring to rule them all please.

On August 28, 2021 10:40:07 PM GMT+02:00, Dmitry Gutov <dgutov@yandex.ru> wrote:
On 28.08.2021 19:28, Theodor Thornhill wrote:
Joking aside, I didn't mean to start a "why isn't my mode in core" thread. The rules just seemed a little arbitrary. Also now with LSP a thing this is more viable than ever. The only benefit would be one off edits wouldn't need a package download.

Good point about LSP, but since it needs an installation from (M)ELPA 
anyway, the only benefit is for one-off edits that somehow don't use the 
main user's setup. Which would seem to be a rare thing to do.

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.