About this Blog

The goal of this blog is to host short, informal articles about the Chapel parallel programming language. Over time, you can expect to see articles teaching language concepts, describing new features or performance results, sharing user experiences, reporting on community events, and other Chapel-related topics. Our intent is that this will be a space for more in-depth content than our Twitter or Facebook feeds can handle, and in more of a browse-at-your-own-speed format than our YouTube channel.

If you’d like to keep up to date with the articles posted on this blog, check out our RSS feed. You can point your newsreader to our feed url to receive full-text articles as they are published.

If there is content you would be interested in seeing on the blog—or an article you’d like to propose writing for it—please let us know in the Chapel Discourse forums. The Discourse Blog Category also serves as our primary way of commenting on blog articles or asking questions about them.

About Chapel

If you’re not familiar with Chapel, it is a general-purpose programming language that makes parallel programming far more productive than conventional approaches. Chapel supports scalable parallelism, permitting code to be developed using a laptop’s multi-core processor, and then recompiled to run across the nodes and cores of a commodity cluster, cloud instance, or massive-scale supercomputer. Though Chapel code tends to be reasonably concise and readable, the resulting performance can compete with or beat standard high-performance computing (HPC) approaches, such as Fortran/C/C++, OpenMP, MPI, and/or CUDA.

If you’re interested in learning more about Chapel, stick around and keep reading! Alternatively, you can browse the Chapel website and/or reach out to the community via Discourse, Gitter, or some other mechanism.