Racket meet-up: Saturday, 6 June 2026 at 18:00 UTC

General
,
1

Everyone is welcome to join us for the :racket: Racket meet-up: Saturday, 6 June 2026 at 18:00 UTC

In your timezone: 2026-06-06T18:00:00Z. (converter).

This meet-up will be held at https://meet.jit.si/Racketmeet-up - note: we may be hitting the maximum number of users that jitsi can support so if you have trouble joining the meeting please let us know.

At this meet-up:

Racket meet-ups are on the first Saturday of EVERY Month at 18:00 UTC

30 minutes but can overrun (it usually lasts ~1hr)

EVERYONE WELCOME :grin:

Stephen :beetle:

λλλ

Spread the word! Share this announcement on social media:

Racket meet-up: Saturday, 6 June 2026 at 18:00 UTC

EVERYONE WELCOME 😁

Announcement, Jitsi Meet link & discussion at https://racket.discourse.group/t/racket-meet-up-saturday-6-june-2026-at-18-00-utc/4275
#lisp #scheme

Meet-up announcements are tagged meet-up
RSS: Racket Discourse - Topics tagged meet-up

λλλ
Racket Discourse Racket Discord
Mastodon Follow Follow Racket on Bluesky chat

See the Racket Calendar for more events - let us know if you are running a Racket meet-up so we can add it !

2

Reminder!

Racket meet-up: Saturday, 6 June 2026 at 18:00 UTC

https://meet.jit.si/Racketmeet-up

3

Thanks everyone who joined the Racket meetup!

We started by talking about Racket meetups in general, especially offline/local ones. There is already a Bay Area meetup coming up: Bay Area Racket Meetup · Luma, and an experimental pub meetup in Scotland: UK Racket meet-up · Luma. Everyone is encouraged to try organizing an offline Racket meetup in their own area.

We also mentioned the RacketCon 2026 call for participation:

Some projects we discussed:

Naturally, we also talked about AI: how people are using it, what helps it produce decent results, and how important fast feedback loops are. Error messages came up as a particularly important part of this, with Rust as one example. This recent paper on verbose errors was mentioned:
https://arxiv.org/pdf/2606.01522

The chess engine comparison led into a broader AI discussion: chess engines used to be weak, but with better algorithms and more hardware, even a phone can now beat the world champion. We discussed whether AI might follow a similar path, including the possibility that in five years useful models could be locally hosted on ordinary machines.

We also talked about the current economics of AI: hardware scarcity, subsidies, token costs, and whether the promised returns on AI investment are realistic. This little site was mentioned:

Related links from that discussion:

On the programming languages side, we mentioned that guaranteed Rust tail-call optimization has been merged into nightly:

We also briefly discussed the take that “every language is either a C or a Lisp”, with JavaScript described as more Lisp-like and Python as more C-like, mostly in terms of how expressions and statements work.

Finally, Justin Slepak showed a demo of implementing reduction rules inspired by the WebAssembly abstract syntax paper:
https://dl.acm.org/doi/pdf/10.1145/3062341.3062363

He followed the small-step reduction rules from the paper and asked for ideas on improving the solution.

Thanks again to everyone who came along and contributed!

2 Likes