Earlier quoted context omitted.
this paper seems fantastic
There are sooooo many goodies coming from the development of Chez scheme (and from Dybvig's students in general).
I stashed many of his publications.
GNU Guile 3.0
11–20 of 64 posts
Re: GNU Guile 3.0
#12The only reason Guile still exists is the stubbornes of GNU project to accept better alternative solutions over the course of time and push their own as the only true.
...which is a great thing if you want to write code that will still run in 30 years. If you're writing code geared toward a company's quarterly report, the long-term doesn't matter, but that's not everyone's goal.
Re: GNU Guile 3.0
#13Excited by the new release. I learned a little bit of Guile for scripting in Make, and I dig it.
It's a little hard to include in my own designs though, as much as I'd like to do it. If I had a wish-list, it would be:
- Make some of the dependencies (especially libgc) internal.
- Reduce the installed size.
- Consider adding a license exception that allows using Guile without inheriting GPLv3's Installation Instructions requirement, which prevents inclusion on a lot of commercial products (even as a standalone program for running scripts).
The Guile team is doing great work, and I'll enjoy trying out 3.0 once it hits my distro packages. I just wish that it slotted better into more systems.
There's some humor in the idea that Guile started out with the stated goal of being a Tcl killer. Years later, a Guile install is almost 8 times the size of a Tcl install and it introduces significant external dependencies. The licensing is also worse for inclusion in larger systems.
Re: GNU Guile 3.0
#14Is there still any work being done on Guile Emacs? As I recall it basically worked a few years ago, but it doesn't seem to be maintained. I'm curious if these 3.0 speedups would translate there too.
Guile runs elisp just fine, although there are quite some low hanging optimization fruit to be picked.
From the Emacs side I strongly doubt it will happen. The discussions that have been going on for faaaar less intrusive changes is staggering. Reading the discussions about the portable dumper (new in the upcoming emacs 27, proposed in 2014) is a nice 4 hours. That was in just about every measurable way a step forward for Emacs, yet it took almost 4 years for it to be mainlined,despite glibc more or less deprecating the old unexec from under emacs' feet.
I might be misrepresenting just about everything here, but one thing I am pretty certain of: guile Emacs will never happen, despite the promises of running elisp on guile.
Re: GNU Guile 3.0
#15Is there still any work being done on Guile Emacs? As I recall it basically worked a few years ago, but it doesn't seem to be maintained. I'm curious if these 3.0 speedups would translate there too.
Guile runs elisp just fine, although there are quite some low hanging optimization fruit to be picked. From the Emacs side I strongly doubt it will happen. The discussions that have been going on for faaaar less intrusive changes is staggering. Reading the discussions about the portable dumper (new in the upcoming emacs 27, proposed in 2014) is a nice 4 hours. That was in just about every measurable way a step forwar…
> Guile runs elisp just fine
While this may be the case, my understanding was that once the codebases were combined and guile-emacs builds were brought online, they encountered a severe performance drop from vanilla Emacs due to back-and-forth string conversion between Guile's Unicode strings and the Emacs internal enhanced string type. I thought that the project was abandoned after finding no obvious resolution to the problem short of a complete rewrite of all Emacs string handling.
Re: GNU Guile 3.0
#16The only reason Guile still exists is the stubbornes of GNU project to accept better alternative solutions over the course of time and push their own as the only true.
I don't really know where you're coming from - Guile is a leading implementation of Scheme. It's valuable by itself.
Re: GNU Guile 3.0
#17Is guile a good choice for going through SICP one day?
Re: GNU Guile 3.0
#18Is there still any work being done on Guile Emacs? As I recall it basically worked a few years ago, but it doesn't seem to be maintained. I'm curious if these 3.0 speedups would translate there too.
Guile runs elisp just fine, although there are quite some low hanging optimization fruit to be picked. From the Emacs side I strongly doubt it will happen. The discussions that have been going on for faaaar less intrusive changes is staggering. Reading the discussions about the portable dumper (new in the upcoming emacs 27, proposed in 2014) is a nice 4 hours. That was in just about every measurable way a step forwar…
I think it could potentially happen by way of a fork, similar to the history of GCC and EGCS, but it would take a dedicated group of hackers to make it happen. Not one guy doing all the work and a bunch of Guile fans on the sidelines cheering for him.
Re: GNU Guile 3.0
#19Is guile a good choice for going through SICP one day?
Yes. You will be able to recreate the examples and problems exactly as they are written using Guile (or any other R6RS-compliant Scheme).
Re: GNU Guile 3.0
#20Earlier quoted context omitted.
Guile runs elisp just fine, although there are quite some low hanging optimization fruit to be picked. From the Emacs side I strongly doubt it will happen. The discussions that have been going on for faaaar less intrusive changes is staggering. Reading the discussions about the portable dumper (new in the upcoming emacs 27, proposed in 2014) is a nice 4 hours. That was in just about every measurable way a step forwar…
> Guile runs elisp just fine While this may be the case, my understanding was that once the codebases were combined and guile-emacs builds were brought online, they encountered a severe performance drop from vanilla Emacs due to back-and-forth string conversion between Guile's Unicode strings and the Emacs internal enhanced string type. I thought that the project was abandoned after finding no obvious resolution to t…
That was only a problem for scheme interop, since guile's elisp uses emacs extended UTF8 strings.