From: Russell Adams <RLAdams@AdamsInfoServ.Com> To: firstname.lastname@example.org Subject: Re: Emacs as an Org LSP server Date: Mon, 14 Dec 2020 19:05:49 +0100 [thread overview] Message-ID: <20201214180549.GE6352@maokai> (raw) In-Reply-To: <email@example.com> On Tue, Dec 15, 2020 at 01:08:47AM +0800, TEC wrote: > > Jean Louis <firstname.lastname@example.org> writes: > > > [LSP is a evil plot from microsoft] > > I can see that you're overly concerned about Microsoft being able to > somehow exert control over this. It may assuage your concerns to see an > example "technology stack" that Org-LSP could fit into. REST API calls to a remote server as a core part of editing text in your editor isn't concerning? How remote? How would you know? If they use HTTPS could you even see what is sent? > Microsoft has provided a /standard/ that a huge number of editors/IDEs > have adopted with /independent implementations/. At this point there is > /nothing/ M$ could do to interfere with how the above works. Microsoft doesn't make standards that it can't corrupt or take advantage of. See LDAP/AD, HTML extensions, programming language extensions that makes their solutions incompatible with standards. > You seem to be focusing on the term "server" in the name. This seems to > be a red herring in this case. In LSP the server is analogous to "emacs > --daemon" and the client to "emacsclient". REST = web server. Using to make JSON requests over what you are editing and your editor requiring the ability to send/receive to a potential remote web server is a valid concern. Emacs daemon is a local socket interface (by default) for communication between processes on the same box. > I appreciate your concerns Jean, and am aware of Microsoft's history, > however I do not believe there is any factual basis for your conclusions > in this instance. Tainted, definitions quoted from https://www.thefreedictionary.com/tainted - To affect or associate with something undesirable or reprehensible: a reputation that was tainted by allegations of illegal activity. - An undesirable or corrupting influence or association: wanted to avoid the taint of an accounting scandal. This is the point. Given Microsoft's shameful history, any project they are supporting is *tainted* by their corrupting influence and association. That LSP is pushed by MS makes it undesirable due to their reputation. That Github is now owned by MS makes it tainted by their reputation. Companies, just like individuals should be judged by their actions. Microsoft's well earned poor reputation is sufficient reason to exclude them from any open source effort. I must conclude that MS is supporting LSP because they believe it will increase market share for their proprietary editors. This is due to their reputation and historic behavior. Thus I have no desire to support LSP and thus not support MS indirectly. You might be tired of this kind of debate, but imagine how those of us who have been in IT for 20 or 30 years are tired of being told that the abuse we have repeatedly endured from MS is somehow no longer relevant. That somehow we're wrong to point out we have suffered abuse from a technology monopoly, and that we are weary and intolerant of those enabling it (ie: govts, CIOs, end users with fancy toys). ------------------------------------------------------------------ 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 18:07 UTC|newest] Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-02 15:05 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 [this message] 2020-12-14 18:12 ` TEC 2020-12-14 19:16 ` Russell Adams 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=20201214180549.GE6352@maokai \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Emacs as an Org LSP server' \ /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
Code repositories for project(s) associated with this 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).