Conversation
Notices
-
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Wednesday, 06-Mar-2024 19:37:47 JST LisPi
@lhp @astrid @dushman Personally I'm not so fond of a number of things about Scheme, but a few in particular are most relevant in this case.
The Scheme standards have effectively no provisions for dynamic introspection, which is a problem when one wants a long-running environment where such introspection capacity would either require adding nonstandard mechanisms (RIP portability) or foregoing them (unacceptable feature degradation).
> used more system libraries (slowly getting there)
That is a good thing exclusively for those libraries which are portable across systems, otherwise it represents a ball & chain for Emacs.
> and shipped less lisp code by default
Destroying Emacs' dynamic reprogramming and modification is a likely outcome of that (particularly given how bad the current Scheme implementations are at it, so even providing a separate REPL to the underlying Scheme isn't enough). That defeats the majority of the point of using it as far as I'm concerned.
I would sooner prefer an Emacs implemented fully in Common Lisp or Interlisp (if one must absolutely avoid CL for whatever reason).- clacke likes this.
-
Embed this notice
lhp (lhp@mastodon.social)'s status on Wednesday, 06-Mar-2024 19:37:49 JST lhp
@lispi314 @dushman @astrid It would be nicer though if it used scheme instead (really sad guile emacs died), used more system libraries (slowly getting there) and shipped less lisp code by default. The last point is not because "bloat", but because if you want non-standard behaviour you have to override a lot of stuff which often feals janky. F.e. evil just does not feel good and it's a popular package. And if you want less popular things like kakoune-like keybinds and the experience is just sad
-
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Wednesday, 06-Mar-2024 19:37:51 JST LisPi
@dushman @astrid It is unfortunately necessary because one has to implement all those workarounds to deal with the garbage system hosting the Emacs Lisp environment.
Normally, one would just be able to rely on the Lisp environment the system provides directly, like OpenGenera.