From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: Emacs as an Org LSP server
Date: Mon, 14 Dec 2020 20:16:49 +0100 [thread overview]
Message-ID: <20201214191649.GH6352@maokai> (raw)
In-Reply-To: <87wnxkntc4.fsf@gmail.com>
On Tue, Dec 15, 2020 at 02:12:43AM +0800, TEC wrote:
> > [ MS Taint ]
>
> I'm a stats student, so if you'll excuse the slightly odd perspective, I
> see the chance of MS being dodgy as a bayesian process. Previous
> knowledge creates an informed prior. It does not allow you to make
> conclusions without examining each instance on a case-by-case basis,
> only predictions. To do otherwise is to commit the genetic fallacy.
I don't credit MS as the source of the idea, only a supporter. So
let's omit MS from the discussion and distill this down.
Emacs is a unique and amazing editor. Emacs has special features that
enables truly remarkable data management and text editing in
Org-mode. Other editors cannot or have not been able to replicate
these features, or Emacs Org-mode would not be so uniquely
desirable. Thus if users want to use Org-mode, they should use
Emacs. It is freely available and like all worthwhile tools Emacs
takes some time to learn.
I understand LSP is about editor agnostic support for common
programming languages and editing operations, reducing code
duplication, and improving editing experience in all editors using
LSP.
As someone using and supporting Emacs, why should I care about LSP?
Perhaps if Emacs lacks a decent editing mode for a language then Emacs
could use LSP to provide missing features.
On the other hand if Emacs can provide an LSP to provide our unique
features to other editors which are not Emacs, does that hurt Emacs?
Emacs and Org are volunteer written and maintained. Volunteer time is
scarce and valuable because it is not paid and the pool of qualified
individuals to provide the specialty labor is small. I don't count
myself among that talent pool, however I advocate for the careful
utilization of their attention and try to contribute from the
sideline.
Given volunteer time for Emacs and Org is valuable, why should that
time be spent on technology that could ultimately decrease Emacs
market share? It seems self defeating to contribute to an effort which
could reduce future interest in Emacs, leading to less volunteer time.
If users and programmers for other editors want to try and replicate
the success and features of Org in their editor, they are welcome to
do so. However why should I want to actively contribute to that
effort?
I see it as a choice between choosing to spend our limited time on
maintaining and improving Emacs and Org, or spend time helping other
editors catch up. This is where MS enters, because they will benefit
and I find that strongly unpalatable.
I do understand I'm being protectionist, yet is that wrong? I support
the idea of other open source editors, but we do compete for users. I
expect other editors to be responsible for implementing their own
features.
If we had more volunteers and a surplus of their valuable time, and
Org didn't struggle for time and attention for maintenance and
improvement, perhaps I would be more supportive of collaborative
efforts between editors. Perhaps I could even ignore that evil
monopolists might indirectly profit.
So in summary, why should anyone contribute to exporting our unique
features to other editors instead of investing that time making Emacs
better?
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2020-12-14 19:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 15:05 Emacs as an Org LSP server TEC
2020-12-13 10:41 ` TEC
2020-12-13 11:05 ` Bill Burdick
2020-12-13 14:36 ` Jean Louis
2020-12-13 17:33 ` TEC
2020-12-13 20:23 ` Jean Louis
2020-12-14 0:54 ` Gerry Agbobada
2020-12-14 1:04 ` Tim Cross
2020-12-14 1:10 ` George Mauer
2020-12-14 11:41 ` Neil Jerram
2020-12-14 15:25 ` TEC
2020-12-14 15:46 ` Neil Jerram
2020-12-14 15:55 ` TEC
2020-12-14 17:02 ` Jean Louis
2020-12-14 17:08 ` TEC
2020-12-14 18:05 ` Russell Adams
2020-12-14 18:12 ` TEC
2020-12-14 19:16 ` Russell Adams [this message]
2020-12-14 20:18 ` Jean Louis
2020-12-14 21:34 ` Tim Cross
2020-12-14 20:20 ` Tim Cross
2020-12-14 21:45 ` Tom Gillespie
2020-12-14 18:39 ` LSP is Microsoft's patented protocol - " Jean Louis
2020-12-14 18:44 ` TEC
2020-12-14 18:52 ` Jean Louis
2020-12-15 5:47 ` Richard Stallman
2020-12-15 5:50 ` Jean Louis
2020-12-15 6:09 ` Christopher Dimech
2020-12-15 6:25 ` Jean Louis
2020-12-15 6:51 ` Christopher Dimech
2020-12-16 5:38 ` Richard Stallman
2020-12-14 17:27 ` Gerry Agbobada
2020-12-14 18:16 ` Jean Louis
2020-12-14 18:26 ` TEC
2020-12-14 18:50 ` Jean Louis
2020-12-14 19:41 ` Russell Adams
2020-12-14 18:51 ` Bastien
2020-12-15 8:51 ` Bill Burdick
2020-12-14 19:50 ` Tim Cross
2020-12-14 21:51 ` Jean Louis
2020-12-14 22:35 ` Dominik Schrempf
2020-12-14 23:36 ` Jean Louis
2020-12-14 17:22 ` Neil Jerram
2020-12-14 17:24 ` TEC
2020-12-14 17:57 ` Neil Jerram
2020-12-14 18:04 ` TEC
2020-12-14 17:39 ` Russell Adams
2020-12-14 17:45 ` TEC
2020-12-16 11:49 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201214191649.GH6352@maokai \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).