From: Arthur Miller <arthur.miller@live.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: tomas@tuxteam.de, emacs-devel@gnu.org
Subject: Re: Gathering data on user preferences
Date: Tue, 07 Sep 2021 20:46:35 +0200 [thread overview]
Message-ID: <AM9PR09MB49774929DB93F0255CCEF52596D39@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <87v93cjoyy.fsf@gmail.com> (Tim Cross's message of "Wed, 08 Sep 2021 02:53:22 +1000")
Tim Cross <theophilusx@gmail.com> writes:
> Arthur Miller <arthur.miller@live.com> writes:
>
>> Tim Cross <theophilusx@gmail.com> writes:
>>
>>> Arthur Miller <arthur.miller@live.com> writes:
>>>
>>>> Tim Cross <theophilusx@gmail.com> writes:
>>>>
>>>>> tomas@tuxteam.de writes:
>>>>>
>>>>>> As a small nit: why JSON and not S-expressions? We're lispies, after
>>>>>> all ;-)
>>>>>>
>>>>>
>>>>> Only because from a web perspective, middleware to process body contents
>>>>> consisting of JSON are plentiful, while libraries for s-expressions are
>>>>> not.
>>>>
>>>> But you would be processing them in Emacs which is very good at processing both
>>>> text and s-expressions? :)
>>>
>>> Why would you be processing them in Emacs? If you had a web service, the
>>> last thing you would have is Emacs sitting behind the web server. You
>>> would use something better suited which would process the data from the
>>> POST request which then stores the data in some format. You might have
>>> Emacs be able to query that data to get reports.
>>
>> Just save a byte stream, and then process in Emacs?
>
> But why? There are loads of libraries which can do all the necessary
> processing and storage of results that would be almost trivial to
> assemble and the data would be processed as soon as it arrives - all
> done without need for human intervention.
Who said human intervention? :-)
I see emacs as a good tool for shell scripting and text processing. In general I
am surprised that lisp(s) are second grade citizens in the land of web scraping,
text processing etc, python being No 1 atm and js no2.
Thomas asked why not s-exps? And I also wonder. If we sent s-exps over the wire,
maybe it would be less processing involved? Write incomming s-exp to emacs
server socket? Is it too wild to think of? :)
> boring task best left to machines I think.
Of course, my thoughts as well, anytime!
next prev parent reply other threads:[~2021-09-07 18:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 3:22 Gathering data on user preferences Tim Cross
2021-09-07 4:25 ` Howard Melman
2021-09-07 6:28 ` Eli Zaretskii
2021-09-07 13:22 ` Howard Melman
2021-09-08 13:37 ` Philip Kaludercic
2021-09-07 6:42 ` tomas
2021-09-07 7:54 ` Tim Cross
2021-09-07 8:11 ` tomas
2021-09-07 9:09 ` Tim Cross
2021-09-07 12:32 ` Arthur Miller
2021-09-07 13:48 ` Tim Cross
2021-09-07 14:52 ` Arthur Miller
2021-09-07 16:53 ` Tim Cross
2021-09-07 18:46 ` Arthur Miller [this message]
2021-09-07 23:14 ` Tim Cross
2021-09-08 7:52 ` Philip Kaludercic
2021-09-08 8:14 ` Tim Cross
2021-09-08 10:41 ` Daniel Fleischer
2021-09-08 13:02 ` Tim Cross
2021-09-08 12:52 ` Philip Kaludercic
2021-09-08 13:00 ` Tim Cross
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=AM9PR09MB49774929DB93F0255CCEF52596D39@AM9PR09MB4977.eurprd09.prod.outlook.com \
--to=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=theophilusx@gmail.com \
--cc=tomas@tuxteam.de \
/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.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).