Welcome to the Chapel language blog! Chapel is a productive language for parallel computing at scale. To learn more, see the welcome article.
Latest posts
-
Transformers From Scratch in Chapel and C++, Part 1
Posted on November 20, 2025
An implementation of a transformer using Chapel, comparing to C++ and PyTorch
-
10 Myths About Scalable Parallel Programming Languages (Redux), Part 8: Striving Toward Adoptability
Posted on November 12, 2025
The eighth and final archival post from the 2012 IEEE TCSC blog series, with a current reflection on it
-
10 Myths About Scalable Parallel Programming Languages (Redux), Part 7: Minimalist Language Designs
Posted on October 15, 2025
The seventh archival post from the 2012 IEEE TCSC blog series, with a current reflection on it
-
Announcing Chapel 2.6!
Posted on September 18, 2025
Highlights from the September 2025 release of Chapel 2.6
-
10 Myths About Scalable Parallel Programming Languages (Redux), Part 6: Performance of Higher-Level Languages
Posted on September 17, 2025
The sixth archival post from the 2012 IEEE TCSC blog series, with a current reflection on it
-
7 Questions for Marjan Asgari: Optimizing Hydrological Models with Chapel
Posted on September 15, 2025
An interview with Dr. Marjan Asgari about her use of Chapel for hydrological research
-
Experimenting with the Model Context Protocol and Chapel
Posted on August 28, 2025
A report on developing MCP-based integrations for the Chapel programming language
-
10 Myths About Scalable Parallel Programming Languages (Redux), Part 5: Productivity and Magic Compilers
Posted on August 20, 2025
The fifth archival post from the 2012 IEEE TCSC blog series, with a current reflection on it
-
7 Questions for Tiago Carneiro and Guillaume Helbecque: Combinatorial Optimization in Chapel
Posted on July 30, 2025
An interview with the two principal developers of ChOp, the Chapel-based Optimization Project
-
10 Myths About Scalable Parallel Programming Languages (Redux), Part 4: Syntax Matters
Posted on July 23, 2025
The fourth archival post from the 2012 IEEE TCSC blog series, with a current reflection on it