Beautiful Racket - Contracts ↗
Beautiful Racket's explainer on Racket contracts shows how contract boundaries protect modules and where blame lands when contracts are violated.
Learning ResourcesA modern Lisp dialect designed for language-oriented programming and education.
Beautiful Racket's explainer on Racket contracts shows how contract boundaries protect modules and where blame lands when contracts are violated.
Learning ResourcesWrite and run Racket code in your browser using Racket 9.1, without installing a local environment.
PlaygroundBeginner explanation of how Racket's contract system works under the hood: runtime enforcement mechanisms, value wrapping, and performance costs.
Learning Resourcesgui-easy is a Racket library for building graphical interfaces declaratively. It provides view components and observable state for connecting application data with widgets. Install the package and run a supplied example, then build a…
Explore project →Koyo is a web application toolkit built on Racket's web server. It provides composable components and project scaffolding for developing web services and applications. Start with the minimal application template, run it locally and add a…
Explore project →Pollen is a publishing system built with Racket. It treats documents as programs, allowing authors to combine text, markup and programmable publishing behaviour. Its source is maintained on GitLab, with a tutorial in the Racket…
Explore project →No community resources are listed yet. Explore all resources.
No current or upcoming events listed. Explore past events or suggest one.
Follow Racket jobs with Atom → Get updates in your feed reader.
No jobs listed right now.
No organizations listed yet.
No curated reading listed yet.
Racket is a general-purpose, multi-paradigm programming language that is a descendant of Scheme, which itself is a dialect of Lisp. Developed to support both academic and practical programming, Racket combines the flexibility of functional programming with powerful macro systems, making it a great tool for experimenting with language design and creating domain-specific languages (DSLs).
Racket’s core features include first-class functions, a rich type system, and a robust macro system, which allows developers to extend the language's syntax and behavior to suit their specific needs. It also offers a comprehensive ecosystem, with built-in support for web programming, GUI development, and scripting, making it versatile for a variety of applications.
While Racket is often used in education to teach programming and computer science concepts, it is also used in research and industry for developing custom solutions and prototyping new programming ideas. Its emphasis on language-oriented programming and its deep connection to the Scheme and Lisp traditions make it a compelling choice for developers interested in functional programming and language design.
Cloudflare built their Topaz formal verification system using Racket and Rosette to prevent DNS configuration conflicts across their global authoritative nameserver infrastructure. The system mathematically proves correctness properties for custom policy programs that determine which IP addresses are returned for DNS queries hitting their network.
The engineering challenge centered on managing conflicting DNS addressing logic from different teams. Multiple systems at Cloudflare could have contradictory views on IP address assignments, and detecting these conflicts manually was unreliable. They needed exhaustive verification that would catch bugs before deployment rather than after production incidents.
Cloudflare chose Racket specifically for its language-oriented programming capabilities. They implemented their topaz-lang DSL interpreter in Racket/Rosette, which translates verification properties into first-order logic formulae that an SMT solver can process. The verifier runs at build time, checking three critical properties: program satisfiability (can this program ever match?), reachability (is this program overshadowed by higher-priority programs?), and exclusivity conflicts (do two exclusive programs match the same queries?). The system verifies seven production programs in six seconds, with microbenchmarks showing 50 programs verified in 300 seconds. When conflicts are detected, the verifier provides concrete example queries demonstrating the conflict, forcing engineers to resolve issues before deployment. This formal verification approach started as a Cloudflare Research project and now runs in production, formally verifying all changes to their authoritative DNS behavior specified in Topaz.
Share a useful Racket project or resource.