emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Elisp LSP Server


From: Jostein Kjønigsen
Subject: Re: Elisp LSP Server
Date: Fri, 5 Nov 2021 07:25:37 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1


On 05.11.2021 06:55, Daniel Brooks wrote:

I admit I wasn’t following the discussion, but I think that it is
becoming more common for people to run large applications inside the
browser.

I admit not following 100% either, but I think the original argument was that users sometimes likes or have the need to edit Emacs LISP-files  outside Emacs, like in online code-forges like GitHub, GitLab and other places.

For the time being these forges, or no editor outside Emacs really, offers adequate support for Emacs LISP.

I guess the argument was that if there was an Emasc LISP LSP-server available for them to use, that might change, and that it could in theory advance the case of Emacs through making Emacs LISP more accessible. If that's how it will turn out in the real world is anyone's guess :)

 
Anyway, VSCode tries to make it as easy as possible for their users to
get started programming in their favorite languages. The VSCode user can
generally go to a list of plugins inside of VSCode, find one for their
language, check the checkbox next to it, and more or less immediately
start programming in that language, complete with LSP integration.

VSCode has seen huge adoptation, also among free software proponents, now being the #1 most popular code-editor in the world (from not even existing 10 years ago).

I believe this aspect here is a very important reason for VSCode having reached the number of users it have.

If we were to apply similar attention to how new Emacs users get started with Emacs, it would most likely affect the amount of new Emacs-users staying around as long-term Emacs users.

A somewhat usable out-of-the-box experience is now considered a pretty fundamental requirement for most software, and not taking that into consideration is by most people considered not viable in the long term.

As far as I
know, Microsoft Office does not give the user the option of exporting
their document as an OpenOffice file, but OpenOffice does allow
exporting documents as Microsoft Office files. Microsoft Office tries to
keep people from straying from Microsoft products, while OpenOffice does
not.

Clearly somewhat off-topic, but Microsoft Office actually offers support for the OpenOffice/LibreOffice OpenDocument file-formats. Both for opening and saving.

When you start Microsoft Office for the first time you are also asked which one of these file-format families you would want to be your default.

I hope something in that ramble was helpful!
Oh certainly. You expressed yourself much more in depth and much clearer than I would, had I answered the same email.

--
Vennlig hilsen
Jostein Kjønigsen

jostein@kjonigsen.net 🍵 jostein@gmail.com 🍵 jostein@hufleslufs.no
https://jostein.kjønigsen.no

reply via email to

[Prev in Thread] Current Thread [Next in Thread]