Post AlS5URA4ZMnnfvKjBI by akater@shitposter.world
 (DIR) More posts by akater@shitposter.world
 (DIR) Post #AlS5UQBoBQb2f18bFQ by lispi314@udongein.xyz
       2024-08-21T20:07:53.490370Z
       
       0 likes, 0 repeats
       
       @wakame @banaanihillo You can write org files by hand. It's really not that hard.It's a bit faster to edit with Emacs, some functions & some settings but it's hardly necessary.The actual reason to not have scripts in Elisp is simply that Emacs is single-threaded and has limited concurrency capacity, so anything that would block should be implemented as something external (lots of things don't subdivide well, so callback hell or idle/timer-based splitting & queuing doesn't work for everything).Elisp is also just a worse Lisp than Common Lisp in general, better implement the programs with that instead.
       
 (DIR) Post #AlS5URA4ZMnnfvKjBI by akater@shitposter.world
       2024-08-29T07:24:56.743879Z
       
       0 likes, 1 repeats
       
       @lispi314 @wakame I think it's not fair to dismiss Elisp as simply being “worse than CL”.  There aro no good compilers yet, there are no conditions, characters are integers, some features are missing, and some behavior is poorly specified, but otherwise it's essentially the same.  Code that is not buffer-specific is easily portable, and even buffer-specific code is often not difficult to port.  I'm loading one my library in both CL and Elisp, from the same source files, and I'm gradually broadening the support for Elisp code in CL.  I also ported ASDF to Elisp, almost completely.