41–46 of 46 posts
Earlier quoted context omitted.
sbcl fails to install? what?
Since decades on windows with foreign locales. The installer just breaks, and self-building fails also. With rpm or apt it works of course, but doesn't feed my interest. clisp also fails on many systems (e.g. libsigsegv on win64), but there I can at least hack it away.
Earlier quoted context omitted.
sbcl fails to install? what?
Since decades on windows with foreign locales. The installer just breaks, and self-building fails also. With rpm or apt it works of course, but doesn't feed my interest. clisp also fails on many systems (e.g. libsigsegv on win64), but there I can at least hack it away.
Are you sure? I use SBCL with Windows with no problem. My machine is localized for spanish language. Also CLISP works just fine.
Clojure. It works very well, I prefer the lisp-1 nature of it to something like Common Lisp, and I really appreciate being able to call out to the JVM (or Javascript, but I don't use ClojureScript at all) for whatever I please. It has Pulsar, which is miles ahead of any other lisp's threading abilities. I wish it had a more mature static typing story, but I guess you can't have everything.
> It has Pulsar, which is miles ahead of any other lisp's threading abilities. What about Lisp Flavored Erlang (LFE)? It was designed for concurrency.
Scheme. Simple, strongly typed, and really really easy to write and read. On top of that, its fairly easy to compile as well, which gets rid of a bunch of distribution problems that come with other Lisps. My first in-production experience was converting a monolithic Python web app to Scheme. We wrote a library that brought a lot of Python conventions over to make things easier. Like an import macro that automatically…
Scheme. Simple, strongly typed, and really really easy to write and read. On top of that, its fairly easy to compile as well, which gets rid of a bunch of distribution problems that come with other Lisps. My first in-production experience was converting a monolithic Python web app to Scheme. We wrote a library that brought a lot of Python conventions over to make things easier. Like an import macro that automatically…
Interesting. Which version of Scheme did you use for this? I really mean the "make", like Chez Scheme or some other, not the version number.
Development is slower than most, because it's mostly a one-man operation, but it's fast, can statically compile, can make tiny binaries and is mostly compliant, and the dev fixes compliance/bugs fairly quickly.
Docs can be lacking at times, but the code is fairly clear.
Earlier quoted context omitted.
Interesting. Which version of Scheme did you use for this? I really mean the "make", like Chez Scheme or some other, not the version number.
Gambit-C. [0] Development is slower than most, because it's mostly a one-man operation, but it's fast, can statically compile, can make tiny binaries and is mostly compliant, and the dev fixes compliance/bugs fairly quickly. Docs can be lacking at times, but the code is fairly clear. [0] https://github.com/gambit/gambit
Also, it was interesting to see that large-scale real-world software has been developed using it.
http://gambitscheme.org/wiki/index.php/Real-world_software_a...