I would like to see wider adoption of Racket. I spent six weeks earlier this year evaluating and comparing Racket, LispWorks Common Lisp, and Swift for an application [1] I am working on. I ended up not choosing Racket, but it was a very close decision. As a modern Lisp, Racket really has it all: vibrant user and dev community, portable GUI support, easy to make standalone applications, and great libraries. [1] http:…
Can you share, what was the deciding factor against Racket?
Racket News – Issue 31
21–28 of 28 posts
Re: Racket News – Issue 31
#22Re: Racket News – Issue 31
#23Earlier quoted context omitted.
Can you share, what was the deciding factor against Racket?
Not OP but for me, I wanted to write http server applications and I was put off by having to specify the http response status messages and timestamps. I'm wondering why something slightly higher level isn't built into the standard lib.
This article might help: https://defn.io/2020/02/12/racket-web-server-guide/
Re: Racket News – Issue 31
#24Earlier quoted context omitted.
Not OP but for me, I wanted to write http server applications and I was put off by having to specify the http response status messages and timestamps. I'm wondering why something slightly higher level isn't built into the standard lib.
You don’t have to specify those things yourself unless you want to manually construct a response struct. There are helpers like response/xexpr and response/output that construct responses for you. This article might help: https://defn.io/2020/02/12/racket-web-server-guide/
Re: Racket News – Issue 31
#25Earlier quoted context omitted.
Can you share, what was the deciding factor against Racket?
Not OP but for me, I wanted to write http server applications and I was put off by having to specify the http response status messages and timestamps. I'm wondering why something slightly higher level isn't built into the standard lib.
Re: Racket News – Issue 31
#26Earlier quoted context omitted.
Not OP but for me, I wanted to write http server applications and I was put off by having to specify the http response status messages and timestamps. I'm wondering why something slightly higher level isn't built into the standard lib.
These days, response status messages are automatically inferred: https://docs.racket-lang.org/web-server/http.html?q=response...
Re: Racket News – Issue 31
#27The videos for the "European Lisp Symposium" appear to just be random 30-second clips. Am I missing something? https://www.twitch.tv/elsconf/videos
[..]Twitch Partners, Twitch Prime and Twitch Turbo users will have their broadcasts saved for 60 days before being deleted. All other broadcasters will have their broadcasts saved for 14 days before they are deleted.[..]
Source: https://help.twitch.tv/s/article/video-on-demand?language=en...
I hope someone made backups. I think are ways to reupload those videos, or make them longer available. I looked at some other streamers archive, and some do have way older videos under the highlights-section available.
Re: Racket News – Issue 31
#28Earlier quoted context omitted.
You don’t have to specify those things yourself unless you want to manually construct a response struct. There are helpers like response/xexpr and response/output that construct responses for you. This article might help: https://defn.io/2020/02/12/racket-web-server-guide/
But if I wanted to say return a 404 I don't want to have to specify "Not Found" along with it every time.
(response/xexpr #:code 404 '(h1 "Not Found"))