3 ms·

The Conrad Barski lisp book used pictures of sheep and wolves to describe Scheme, Lisp, and Haskell iirc. Also cavemen to describe Fortran I think lol. I think

The Conrad Barski lisp book used pictures of sheep and wolves to describe Scheme, Lisp, and Haskell iirc. Also cavemen to describe Fortran I think lol. I think he was trying to show scheme as being more elegant than common lisp, but also significantly less practical.

packetlost 3y ago
I feel like Racket sorta changed the "practicality" story in many respects for Scheme. Not in the sense that Racket itself is practical, but the macro system is really good and inspired other Schemes like Gerbil that are more practical.
tomcam 3y ago
[flagged]
vincent-manis 3y ago
I would be able to speak to the allegedly “impractical” nature of Scheme if only I knew why Cisco hired Kent Dybvig, the principal developer of Chez Scheme. I would also like to know why Beckman Coulter Life Sciences supported the development of Swish, an extension of Chez Scheme that provides Erlang-inspired message passing. Gambit and Scheme have been used for health applications. Here's one paper on that subject, from 2013: https://ecem.ece.ubc.ca/~cpetersen/lambdanative_icfp13.pdf https://ecem.ece.ubc.ca/~cpetersen/lambdanative_icfp13.pdf I would mention the use of GNU Guile to build Guix, which has had considerable uptake. Guile has been used to build other Linux programs. Admittedly, Scheme isn't widely used. But impractical? No!
- varjag 3y ago
  …if only I knew why Cisco hired Kent Dybvig… Nobody knows really but my suspicion it's not for moving Cisco codebase to Scheme.
- lispm 3y ago
  The impression of being 'impractical' came from the Scheme reports, which for a long time, with the exception of the controversial R6RS, only standardized a relatively simple/limited language (example: no error handling).
- 7thaccount 3y ago
  Probably impracticality via ecosystem. Chez scheme is fast, but more limited library wise than common lisp and much more limited than Python in that manner. Note that I like Chez scheme and think it's really cool.
- MattHeffron 3y ago
  why Beckman Coulter Life Sciences supported the development of Swish, an extension of Chez Scheme Having worked at Beckman¹ from 1978-2022, I strongly suspect that the support of a Scheme-based system was due to the educational background of several of the senior developers in that group of the Life Sciences software development team. ¹ Beckman Instruments -> SmithKline Beckman -> Beckman Instruments -> Beckman Coulter -> Beckman Coulter acquired by Danaher 2011 -> Beckman Coulter Capillary Electrophoresis business moved (2013) to AB Sciex (also a Danaher company)

packetlost 3y ago

I feel like Racket sorta changed the "practicality" story in many respects for Scheme. Not in the sense that Racket itself is practical, but the macro system is really good and inspired other Schemes like Gerbil that are more practical.

tomcam 3y ago

[flagged]

vincent-manis 3y ago

I would be able to speak to the allegedly “impractical” nature of Scheme if only I knew why Cisco hired Kent Dybvig, the principal developer of Chez Scheme. I would also like to know why Beckman Coulter Life Sciences supported the development of Swish, an extension of Chez Scheme that provides Erlang-inspired message passing. Gambit and Scheme have been used for health applications. Here's one paper on that subject, from 2013: https://ecem.ece.ubc.ca/~cpetersen/lambdanative_icfp13.pdf https://ecem.ece.ubc.ca/~cpetersen/lambdanative_icfp13.pdf I would mention the use of GNU Guile to build Guix, which has had considerable uptake. Guile has been used to build other Linux programs. Admittedly, Scheme isn't widely used. But impractical? No!

varjag 3y ago
…if only I knew why Cisco hired Kent Dybvig… Nobody knows really but my suspicion it's not for moving Cisco codebase to Scheme.
lispm 3y ago
The impression of being 'impractical' came from the Scheme reports, which for a long time, with the exception of the controversial R6RS, only standardized a relatively simple/limited language (example: no error handling).
7thaccount 3y ago
Probably impracticality via ecosystem. Chez scheme is fast, but more limited library wise than common lisp and much more limited than Python in that manner. Note that I like Chez scheme and think it's really cool.
MattHeffron 3y ago
why Beckman Coulter Life Sciences supported the development of Swish, an extension of Chez Scheme Having worked at Beckman¹ from 1978-2022, I strongly suspect that the support of a Scheme-based system was due to the educational background of several of the senior developers in that group of the Life Sciences software development team. ¹ Beckman Instruments -> SmithKline Beckman -> Beckman Instruments -> Beckman Coulter -> Beckman Coulter acquired by Danaher 2011 -> Beckman Coulter Capillary Electrophoresis business moved (2013) to AB Sciex (also a Danaher company)