From eaab7a58f3d2cd7ea0d35ad3d29f5e09db91de5e Mon Sep 17 00:00:00 2001
From: Sacha Chua <sacha@sachachua.com>
Date: Tue, 4 Jul 2023 23:26:08 -0400
Subject: llm and lspocaml talk descriptions

---
 2023/talks/llm.md | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 2023/talks/llm.md

(limited to '2023/talks/llm.md')

diff --git a/2023/talks/llm.md b/2023/talks/llm.md
new file mode 100644
index 00000000..0f5f22d3
--- /dev/null
+++ b/2023/talks/llm.md
@@ -0,0 +1,38 @@
+[[!meta title="LLM clients in Emacs, functionality and standardization"]]
+[[!meta copyright="Copyright &copy; 2023 Andrew Hyatt"]]
+[[!inline pages="internal(2023/info/llm-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# LLM clients in Emacs, functionality and standardization
+Andrew Hyatt (he/him)
+
+| Email | <ahyatt@gmail.com> |
+| Mastodon | <https://urbanists.social/@ahyatt> |
+| Github | <http://github.com/ahyatt> |
+
+[[!inline pages="internal(2023/info/llm-before)" raw="yes"]]
+
+As an already powerful way to handle a variety of textual tasks, Emacs
+seems unique well poised to take advantage of Large Language Models
+(LLMs).  We'll go over what LLMs are and are used for, followed by listing
+the significant LLM client packages already for Emacs.  That functionality
+that these packages provide can be broken down into the basic features that
+are provided through these packages.  However, each package currently is
+managing things in an uncoordinated way.  Each might support different LLM
+providers, or perhaps local LLMs.  Those LLMs support different
+functionality.  Some packages directly connect to the LLM APIs, others use
+popular non-Emacs packages for doing so.  The LLMs themselves are evolving
+rapidly.  There is both a need to have some standardization so users don't
+have to configure their API keys or other setup independently for each
+package, but also a risk that any standardization will be premature.  We
+show what has been done in the area of standardization so far, and what
+should happen in the future.
+
+[[!inline pages="internal(2023/info/llm-after)" raw="yes"]]
+
+[[!inline pages="internal(2023/info/llm-nav)" raw="yes"]]
+
+
-- 
cgit v1.2.3