Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://sfba.social/users/kickingvegas/statuses/113726122002655972">Charles Choi 최 민수 (kickingvegas@sfba.social)'s status on Saturday, 28-Dec-2024 03:30:47 JST</a><a href="https://sfba.social/@kickingvegas" title="kickingvegas@sfba.social"><img src="https://gnusocial.jp/avatar/160782-48-20241106023618.webp" width="48" height="48" alt="Charles Choi 최 민수" style="position: absolute; left: 0; top: 0;">Charles Choi 최 민수</a><div><a href="https://sfba.social/@kickingvegas/113723373781728507" rel="in-reply-to">in reply to</a></div></section><article><p>These three links have informed a lot of my thinking of late on writing Elisp, which I am admittedly novice at. The quoted paragraph in the first link on the chaos of using a map-style (key, value) collection is especially resonant to me. I personally don't care to please old Elisp heads who say we should only use builtins. I want to use conventional abstractions that are shared among the languages I know like Python, Swift, JavaScript, and Java. </p><p><a href="https://www.murilopereira.com/emacs-from-catching-up-to-getting-ahead#5-emacs-lisp-improvements" rel="nofollow noreferrer">https://www.murilopereira.com/emacs-from-catching-up-to-getting-ahead#5-emacs-lisp-improvements</a></p><p><a href="https://lmno.lol/alvaro/modern-elisp-libraries" rel="nofollow noreferrer">https://lmno.lol/alvaro/modern-elisp-libraries</a></p><p><a href="https://www.wilfred.me.uk/blog/2013/03/31/essential-elisp-libraries/" rel="nofollow noreferrer">https://www.wilfred.me.uk/blog/2013/03/31/essential-elisp-libraries/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4265891#notice-8337187">In conversation</a><time datetime="2024-12-28T03:30:47+09:00" title="Saturday, 28-Dec-2024 03:30:47 JST">about 4 months ago</time> <span>from <span><a href="https://sfba.social/@kickingvegas/113726122002655972" rel="external" title="Sent from sfba.social via ActivityPub">sfba.social</a></span></span><a href="https://sfba.social/@kickingvegas/113726122002655972">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: www.murilopereira.com</div><h5><a href="https://www.murilopereira.com/emacs-from-catching-up-to-getting-ahead#5-emacs-lisp-improvementshttps://lmno.lol/alvaro/modern-elisp-librarieshttps://www.wilfred.me.uk/blog/2013/03/31/essential-elisp-libraries/">Emacs: from catching up to getting ahead</a></h5><div></div></header><div>What does Emacs need for us to someday run M-x neuralink-mode and evaluate Lisp in the brain?</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Charles Choi 최 민수 (kickingvegas@sfba.social)'s status on Saturday, 28-Dec-2024 03:30:47 JST Charles Choi 최 민수
in reply to
These three links have informed a lot of my thinking of late on writing Elisp, which I am admittedly novice at. The quoted paragraph in the first link on the chaos of using a map-style (key, value) collection is especially resonant to me. I personally don't care to please old Elisp heads who say we should only use builtins. I want to use conventional abstractions that are shared among the languages I know like Python, Swift, JavaScript, and Java.
https://www.murilopereira.com/emacs-from-catching-up-to-getting-ahead#5-emacs-lisp-improvements
https://lmno.lol/alvaro/modern-elisp-libraries
https://www.wilfred.me.uk/blog/2013/03/31/essential-elisp-libraries/
In conversationabout 4 months ago from sfba.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: www.murilopereira.com
  Emacs: from catching up to getting ahead
  What does Emacs need for us to someday run M-x neuralink-mode and evaluate Lisp in the brain?

Public

Embed Notice

HTML Code

Corresponding Notice