Russell Adams <rlad...@adamsinfoserv.com> writes:
> 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? I'm not concerned about REST API calls to a remote server, because: 1. There are no REST API calls 2. There is no remote server > 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. Sure, but I can choose not to support a certain standard, as can other LSP-Client/Server FLOSS devs, and you can install a particular version of either. > 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. No REST, just JSON-RPC, which is just a data format. I don't think JSON is evil. Oh, and once again, no web servers. > Emacs daemon is a local socket interface (by default) for > communication between processes on the same box. Yep, like LSP. Hence the analogy. > [ 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. -- Timothy
