| ▲ | BeetleB 5 hours ago | ||||||||||||||||
I speak only for myself and not the Emacs team, but ... IMO it shouldn't do this by default - unless there is a clear "winner" among all the choices. IIRC, for eglot I had to install a Python language server. There are a bunch of them. Why would I want it to pick one by default? I don't know if Emacs will ever have an IDE with TS and LSP working "out of the box" without some configuration. From my experience with Eglot, if it were enabled by default, it would confuse the heck out of some users who just want to, say, edit a Python script. There are always opinionated releases like Doom Emacs or Spacemacs that can set whatever nice defaults you think should be there. Leave vanilla Emacs to be, well, vanilla. Emacs, while it can be a decent IDE, is not an IDE and shouldn't default to being one. | |||||||||||||||||
| ▲ | KallDrexx 5 hours ago | parent | next [-] | ||||||||||||||||
I recently switched from full IDE to Emacs (wrote up about the things I learned at https://github.com/KallDrexx/emacs-zero-to-ide-journey/blob/...) Typescript is a perfect example of why Emacs shouldn't own that setup. Typescript version 6 uses the "typescript-language-server" which is a totally stand alone nom package for lsp support. Typescript 7, is incompatible with typescript-language-server and the compiler itself now acts as a lsp. If Emacs handles that all by default it then needs to handle versioning of each language server itself across all operating systems, handle cases when different machines have different npm version managers, upgrades, etc... It's not impossible but it's a lot to ask, and it requires more frequent version upgrades just to keep things in sync. I couldn't even use the built in version of eglot and had to use ELPA version for bug fixes that affect c# LSP support that were committed to the package back in December. | |||||||||||||||||
| |||||||||||||||||
| ▲ | dleslie 5 hours ago | parent | prev [-] | ||||||||||||||||
Emacs makes many opinionated choices about defaults; if it didn't, it would launch to little more than an elisp REPL by default. What's important is that _you can change it_. Good defaults ensure that Emacs doesn't repel new users and casual users and users who are not interested in fiddling. And this isn't a matter of color theme default, or font default; this is a shipped feature that _does not function_ without changes to the defaults! By default, it does not work. | |||||||||||||||||
| |||||||||||||||||