From: Tim Cross <theophilusx@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-tangents@gnu.org
Subject: Re: Elisp LSP Server
Date: Sat, 23 Oct 2021 08:58:47 +1100 [thread overview]
Message-ID: <m2v91o1ynk.fsf@blind-drunk.fritz.box> (raw)
In-Reply-To: <CADwFkmnAVWPTnkwqPqsuWY2LQo4eL_VJTqvXRBS+ouMxWUFQrA@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> (Moved to emacs-tangents.)
>
> Tim Cross <theophilusx@gmail.com> writes:
>
>> I also think what is really needed in the free software community is
>> [...] a well designed free javascript library which would facilitate
>> the development of web UIs that would allow sites like
>> savannah.gnu.org to have an interface as functional and modern looking
>> as github using free software.
>
> What's wrong with e.g. React (MIT License) or Angular (MIT License)?
There is quite a bit considered "wrong" about the MIT License (see the
GNU Project page on free licenses). However, I probably should have said
"framework" rather than library. The problem with both react and angular
is that much of the time, sites are created based on those technologies,
but using higher level abstractions for components or infrastructure
that sit on top of a react or angular base which do not have free
licenses.
What I was meaning to say is that what is needed is a free technology
stack where all the components - e.g. authentication layer, middleware,
model/database, ui/view components and controllers are all free
software and which have appropriate free software licenses.
prev parent reply other threads:[~2021-10-22 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16338bdc2497fc51c6fb6d54ab370bfb@webmail.orcon.net.nz>
[not found] ` <CABrcCQ4i3t8HjAAm_iYe2JU-ZBBa7mb_ukfiW6MCp6T6sV0JoQ@mail.gmail.com>
[not found] ` <9eb888e1-1342-46b1-b4be-32d49cd7a74d@yandex.ru>
[not found] ` <1656272.pu0UoWQkng@galex-713.eu>
[not found] ` <m2zgr024d5.fsf@blind-drunk.fritz.box>
2021-10-22 21:09 ` Elisp LSP Server Stefan Kangas
2021-10-22 21:58 ` Tim Cross [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2v91o1ynk.fsf@blind-drunk.fritz.box \
--to=theophilusx@gmail.com \
--cc=emacs-tangents@gnu.org \
--cc=stefankangas@gmail.com \
/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.
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).