[ prog / sol / mona ]

prog


Scheme blogs

1 2019-12-26 15:50

https://www.wingolog.org/

2 2019-12-31 08:55 *

http://matt.might.net/articles/

3 2020-02-08 11:14

RSS aggregator for Scheme blogs: http://scheme.dk/planet/

4 2020-02-26 19:01 *

https://hyper.dev/

5 2020-02-26 19:43 *

https://ambrevar.xyz/index.html

6 2020-04-02 07:05 *

https://weinholt.se/

7 2020-07-26 18:16 *

https://jeko.writeas.com/

8 2021-03-22 17:13

Planting Flowers in Guile

http://muto.ca/posts/planting-flowers-in-guile.html

9 2021-03-27 21:48

Evolution of a Scheme programmer

https://erkin.party/blog/200715/evolution/

10 2021-07-29 11:53

Beautiful ideas in programming: generators and continuations

https://www.hhyu.org/posts/generator_and_continuation/

11 2021-09-24 15:29

>>1
Someone tell Andy to update their certificate!

12 2021-09-25 10:58

https://blog.racket-lang.org

13 2021-10-06 05:38

https://lispcast.com/what-is-the-curse-of-lisp/

14 2021-10-06 08:04

The Bipolar Lisp Programmer

http://www.marktarver.com/bipolar.html

15 2021-10-06 17:27

>>13
Why doesn't the curse of Lisp apply to elisp?

16 2021-10-07 07:30 *

>>15
Elisp is the worst lisp, any of lisps power is undermined by the 99 interface into weird c gnu code for a faulty lisp machine with nonaligned virtual Qhardware.
Elisp has the curse of being a overconfigurable programmer environment see acme plumber plan9 and vim :! tmux. This leads to the majority of programmers not making extensions and using the defaults or using some bloated package of preconfigured extensions. QED users are more productive.

17 2022-06-11 20:34

>>13-16
https://applied-langua.ge/posts/lisp-curse-redemption-arc.html
The curse of Lisp does not actually exist.

18 2022-06-12 16:05

>>13
I know that's a transcript but it reads like it was written by a 10 year old. And it doesn't even make much sense: people spend countless "people hours" because their tools are so painful to use so they're more motivated/committed than they would if things were easier?
Who's this dumb fuck?

19 2022-06-12 18:51 *

>>17
TL;DR

It's about time, then, that we just shut up about this "curse",

NO, as long as LISP is still a second class resident in the unix cage.

and get some work done!

YES?

20 2022-06-12 20:23 *

as long as LISP is still a second class resident in the unix cage.

What does that have to do with the ``curse''?

21 2022-06-13 01:22

If you are reading this post all summer /sol/stice fags have invaded prog. To undo this curse you need to copy this and paste it in 20 other threads. I'm so, so sorry, please forgive me.

22 2022-06-13 08:56 *

i am a heron. i ahev a long neck and i pick fish out of the water w/ my beak. if you dont repost this comment on 10 other pages i will fly into your kitchen tonight and make a mess of your pots and pans

23 2022-06-13 21:03 *

>>22
I love birds, I'd love to see a heron that close! Totally worth the mess!

24 2022-06-13 23:04 *

>>20

> The real question is if Lisp is so powerful, if it's such a great language, and it lets you do so much, why isn't it more popular? It's not about the parentheses. [...] A lot of it is the market forces, if you will.
As we have suggested before, we do want a Lisp operating system, but the special machines are less necessary with clever compilation strategies today; [blame your ancestry and the market.]

They think they have done a lot, way more enough than have to break out of the cage, to unlease the full power of lisp, to build an environment (os and/or hardware) where Lispers engage in more collaboration, processes are lambdas, memory management is done more elegantly&securely and then everyone uses better naming convention & make decent documentation (for the system core at the very least), avoids deep nested code blocks w/o comments like a plague and remembers to include the test suites certainly needed by a community. And God some become Clojurists then defect to the JVM!

25 2022-06-13 23:34 *

>>20

There are two apparent "solutions" that avoid this curse that we will explore. The first solution is to add the extension to the system via the implementation, forcing the community to adopt this extension, removing the agency of the user and setting them up to be screwed if the solution becomes a problem. The second is to ensure that any task is too large to tackle without cooperation, by reducing the power and efficiency of each individual user, and in doing so, eliminating all facilities for the individual creative process.

Neither solution is particularly appealing.

[blahblahblah discouraging opinions]

The most viable option is to go forward with multiple experiments, and provide participants with more power, so they may late bind and ignore the "social problems" produced by the diverse environment, in turn provided by having reasonable control over the environment.

Sounds like the chicken&egg discussion.

26 2022-06-14 17:46 *

Does it have to be Scheme only?

27 2022-07-07 06:41

A Scheme Primer
https://spritely.institute/static/papers/scheme-primer.html

28 2022-07-08 17:59

This seems pretty fun: https://idiomdrottning.org/sexpc

29 2022-07-10 06:35

>>28
base64 encoded backup of the Git bundle: https://paste.textboard.org/eb7d73f4

30 2022-07-10 09:14

Guile Steel: a proposal for a systems lisp

https://dustycloud.org/blog/guile-steel-proposal/
Why not rewrite Rust in Scheme??

31


VIP:

do not edit these