Can anyone tell me if Guile is relevant? The list of example programs written in Guile is small. EmacsLisp and not Scheme seems to be the Gnu lisp of choice. The VM is not the fastest and not the most portable. Is there any driver behind it?
GNU Guile 2.2.0
91–100 of 149 posts
Re: GNU Guile 2.2.0
#92Earlier quoted context omitted.
There’s still work to be done in pre-compiling the elisp in Guile Emacs to reduce the starttime (a lot).
I never understood why people care so much about Emacs' start time. I start emacs maybe once a month and I'd say that anyone who's starting their Emacs so often that start time becomes a nuisance isn't using Emacs the way it's supposed to be used.
Re: GNU Guile 2.2.0
#93Earlier quoted context omitted.
Technical question: What are .lz files? Is this LZMA compression? If so, why not using the more popular .xz format?
I'm not sure but probably because it produced a smaller file than xz.
These days, some distros use lz and most use xz, probably mostly due to historical reasons.
Re: GNU Guile 2.2.0
#94Earlier quoted context omitted.
Yes. It's the second-oldest high level programming language (after Fortran). - Fortran: 1957 - Lisp: 1958 - ... - C: 1972
I mean to say lisp family. so Fortran counts as part of C family.
Re: GNU Guile 2.2.0
#95To try out Guile 2.2.0 easily from any GNU/Linux distro (from the full release notes): Bonus track! This release also contains a new experiment, a binary installation package for the x86_64 architecture. The GNU Guix project (https://guixsd.org/) has assembled a graph of package definitions (for example, GCC, glibc, Guile, and so on) and is able to build that graph in an entirely deterministic way starting from only…
Technical question: What are .lz files? Is this LZMA compression? If so, why not using the more popular .xz format?
tl;dr: Because apparently some people believe that not only can they afford to exclude some users by avoiding zip's, but they must also bike-shed some more.
Re: GNU Guile 2.2.0
#96Earlier quoted context omitted.
Besides being controlled by GNU, not really. Guilemacs is probably not going to happen either. I like Emacs and all, but I'm really not sure why we'd be excited about Guile. Andy is a really awesome guy but he's the only one contributing to Guile, so there's no way it's ever going to compete with things like Chez or Racket (which is moving to Chez soon as well).
Andy is not the only one contributing to Guile. He does a ton, for sure, but Guile is far from a one man show. There are 2 other maintainers and many other contributors.
Are you saying this is inaccurate? Andy is far and away the top contributor, it's not even close. It really does seem to be a one man show.
Re: GNU Guile 2.2.0
#97Earlier quoted context omitted.
Sure, functions can do that and more (borrowing a page from Smalltalk): (if* cond #'(lambda () then) #'(lambda () else)) All the macro does is eliminate the need to write out all the lambda syntax. (defmacro (if cond then else) `(if* ,cond #'(lambda () ,then) #'(lambda () ,else))) This brings my back to my original point: "the extent of the logic encoded in macros should be minimized, with the macros translating the…
I do not agree that an if macro stands for some specific lambda-based utterance. That isn't historically true, or in any other sense. The macro potentially stands for any and every possible way in which its semantics can be achieved.
Huh? Are you saying the use of lambdas does NOT give if* the ability to control the execution of 'then' and 'else'?
My point is that if you're concerned about how often you evaluate a block of code (0, 1, or n times), there are ways to achieve this goal that do not require macros. (And consequently, the macros mainly serve as they should: to clean up the syntax, if necessary.)
Re: GNU Guile 2.2.0
#98Any word about Windows support?
Re: GNU Guile 2.2.0
#99Earlier quoted context omitted.
I never understood why people care so much about Emacs' start time. I start emacs maybe once a month and I'd say that anyone who's starting their Emacs so often that start time becomes a nuisance isn't using Emacs the way it's supposed to be used.
So it's not supposed to be started often? Where does it say that?