From: Jean Louis <bugs@gnu.support>
To: Andrew Goh <andrewgoh2032@yahoo.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Enhancing ELisp for AI Work
Date: Mon, 16 Dec 2024 16:39:26 +0300 [thread overview]
Message-ID: <Z2AtjpDH0irAol4g@lco2> (raw)
In-Reply-To: <7290780.2375960.1734348492938@mail.yahoo.com>
* Andrew Goh via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2024-12-16 14:30]:
> As a long-time Emacs user and enthusiast, I would like to recommend
> that the team consider enhancing ELisp to make it more suitable for
> artificial intelligence (AI) work.
That is so true. Though, if you think on LLMs, then I am in
disagremeent calling Large Language Models solely AI, it is better we
specify it well what we mean with it. The word AI now became a popular
keyword for common people to interact with computer and get some tasks
done by using Natural Language Processing.
ALL COMPUTER PROGRAMS EMBODY ASPECTS OF ARTIFICIAL INTELLIGENCE!
Isn't that main reason why we are programming?
> Elisp has been an incredibly powerful and flexible language for
> Emacs extension development, but its capabilities can be further
> expanded to support AI applications.
Oh, absolutely yes.
> Some potential areas for enhancement include:
> 1. Performance improvements through Just-In-Time (JIT) compilation
> or native code generation.
Hmm, I have no idea of JIT within Emacs and if that would at all speed
it up, but it does have "native compilation" now, though unsure how it
works. It makes it a bit faster I guess. Maybe that is what you mean.
In fact before generating questions with the LLM, maybe you should
cross check with your own skills if the feature you are querying
already implemented in Emacs.
> 2. Introduction of native numerical arrays and linear algebra
> libraries
Personally, no idea on that. What I know is that mathematics works
well within Emacs.
> 3. Development of machine learning and AI libraries, including
> neural networks, decision trees, and clustering algorithms
I guess now there is nothing within Emacs for that, but we can always
🚀 call external functions and speed up the overall development cycle
by working through the portal of GNU Emacs. 💻🔍
> 4. Improved interoperability with other languages through a foreign
> function interface (FFI)
Not sure about that, but now Emacs has modules, so anything is
possible to hook into it.
LLM information is there to provide guidelines, not to be smarter than
you and especially can't outsmart people on the mailing list.
Here is easily to find Emacs FFI module:
https://github.com/tromey/emacs-ffi
Looks like your LLM has been playing chess with your brain and winning
every game!
A second or few was the information that Emacs FFI already exists.
> 5. Enhanced documentation and community resources focused on AI
> development in ELisp
People have been developing AI since the inception of computers, and
also Emacs and GNU Operating System, and as you know, without GNU,
there would be no Linux, there would be no Ruby, Python, etc., and so
on—it is all a big chicken and many eggs now.
> By addressing these areas, ELisp can become a more comprehensive and
> efficient platform for AI development, attracting a wider range of
> users and developers.
I think it is excellent editing platform already, and is being very
much addressed.
You see, it does matter how you write, as to say "by addressing these
areas" while many are already addressed it may appear wronging and
invalidating. As I said, the LLM response outsmarted you 😎
> Andrew Goh S MWith Help from Meta AI
Next time try with your own built-in I.
--
Jean Louis
next prev parent reply other threads:[~2024-12-16 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7290780.2375960.1734348492938.ref@mail.yahoo.com>
2024-12-16 11:28 ` Enhancing ELisp for AI Work Andrew Goh via Users list for the GNU Emacs text editor
2024-12-16 13:39 ` Jean Louis [this message]
2024-12-16 14:55 ` Tomáš Petit
2024-12-16 16:26 ` Jean Louis
2024-12-16 17:38 ` Jean Louis
2024-12-17 6:24 ` Tomáš Petit
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=Z2AtjpDH0irAol4g@lco2 \
--to=bugs@gnu.support \
--cc=andrewgoh2032@yahoo.com \
--cc=help-gnu-emacs@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.
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).