chapel-lang · bradcray · Nov 13, 2025 · Nov 8, 2025 · Nov 12, 2025 · Nov 13, 2025
diff --git a/content/posts/10myths-part1/index.md b/content/posts/10myths-part1/index.md
@@ -3,7 +3,7 @@ title: "10 Myths About Scalable Parallel Programming Languages (Redux),  Part 1:
 date: 2025-04-30
 tags: ["Editorial", "Archival Posts / Reprints", "Sparse Arrays"]
 series: ["10 Myths About Scalable Parallel Programming Languages Redux"]
-summary: "An archival post from the IEEE TCSC blog in 2012 with a current reflection on it"
+summary: "An archival post from the IEEE TCSC blog in 2012, with a current reflection on it"
 authors: ["Brad Chamberlain"]
 ---
 
@@ -381,7 +381,7 @@ Tune in next time for more myths about scalable parallel programming languages.
 
 [1] B. L. Chamberlain, D. Callahan, H. P. Zima, [Parallel
 Programmability and the Chapel
-Language](http://hpc.sagepub.com/content/21/3/291.abstract),
+Language](https://hpc.sagepub.com/content/21/3/291.abstract),
 _International Journal of High Performance Computing Applications_,
 August 2007, 21(3): 291–312.
 
@@ -506,7 +506,7 @@ to be 64 bits in Chapel—almost like I was trying to go out of my way
 to make it more verbose.  That said, I can also think of users who
 tend to prefer that additional level of explicitness in their code.
 
-#### Wrapping Up
+### Wrapping Up
 
 All in all, I think the premise of the original article holds up and
 that, by and large, the features we had designed for Chapel in 2012

diff --git a/content/posts/10myths-part2/index.md b/content/posts/10myths-part2/index.md
@@ -3,7 +3,7 @@ title: "10 Myths About Scalable Parallel Programming Languages (Redux),  Part 2:
 date: 2025-05-28
 tags: ["Editorial", "Archival Posts / Reprints", "GPU Programming"]
 series: ["10 Myths About Scalable Parallel Programming Languages Redux"]
-summary: "Another archival post from the IEEE TCSC blog in 2012 with a current reflection on it"
+summary: "Another archival post from the IEEE TCSC blog in 2012, with a current reflection on it"
 authors: ["Brad Chamberlain"]
 ---
 
@@ -495,7 +495,7 @@ language design discussions during those years, and the positive
 impact they had on Chapel.
 
 
-#### Wrapping Up
+### Wrapping Up
 
 That wraps up this month's article.  While its focus on HPF may seem
 dated, I think the content remains interesting by capturing some of

diff --git a/content/posts/10myths-part3/index.md b/content/posts/10myths-part3/index.md
@@ -3,7 +3,7 @@ title: "10 Myths About Scalable Parallel Programming Languages (Redux),  Part 3:
 date: 2025-06-25
 tags: ["Editorial", "Archival Posts / Reprints", "GPU Programming"]
 series: ["10 Myths About Scalable Parallel Programming Languages Redux"]
-summary: "A third archival post from the 2012 IEEE TCSC blog series with a current reflection on it"
+summary: "A third archival post from the 2012 IEEE TCSC blog series, with a current reflection on it"
 authors: ["Brad Chamberlain"]
 ---
 
@@ -613,7 +613,7 @@ of ubiquitous parallel computing and ride it to widespread adoption,
 as Fortran did with optimizing compilers or Java did with the web.
 
 
-#### Wrapping Up
+### Wrapping Up
 
 That concludes this month's myth about the non-adoptability of new
 languages and particularly languages that aren't extensions of others.

diff --git a/content/posts/10myths-part4/index.md b/content/posts/10myths-part4/index.md
@@ -3,7 +3,7 @@ title: "10 Myths About Scalable Parallel Programming Languages (Redux),  Part 4:
 date: 2025-07-23
 tags: ["Editorial", "Archival Posts / Reprints"]
 series: ["10 Myths About Scalable Parallel Programming Languages Redux"]
-summary: "The fourth archival post from the 2012 IEEE TCSC blog series with a current reflection on it"
+summary: "The fourth archival post from the 2012 IEEE TCSC blog series, with a current reflection on it"
 authors: ["Brad Chamberlain"]
 ---
 
@@ -438,7 +438,7 @@ that rely on using an outer array's indices to parameterize an inner
 array's domain.  The other declarations would work fine.
 
 
-#### Wrapping Up
+### Wrapping Up
 
 That concludes this month's myth about whether syntax matters when
 designing scalable parallel programming languages.  I definitely

diff --git a/content/posts/10myths-part5/index.md b/content/posts/10myths-part5/index.md
@@ -3,7 +3,7 @@ title: "10 Myths About Scalable Parallel Programming Languages (Redux),  Part 5:
 date: 2025-08-20
 tags: ["Editorial", "Archival Posts / Reprints"]
 series: ["10 Myths About Scalable Parallel Programming Languages Redux"]
-summary: "The fifth archival post from the 2012 IEEE TCSC blog series with a current reflection on it"
+summary: "The fifth archival post from the 2012 IEEE TCSC blog series, with a current reflection on it"
 authors: ["Brad Chamberlain"]
 ---
 
@@ -579,7 +579,7 @@ analyze, but this too remains future work.
 
 
 
-#### Wrapping Up
+### Wrapping Up
 
 That concludes this month's myth about how well-designed, productive
 languages need not rely on magic or heroic compilers to get things

diff --git a/content/posts/10myths-part6/index.md b/content/posts/10myths-part6/index.md
@@ -3,7 +3,7 @@ title: "10 Myths About Scalable Parallel Programming Languages (Redux),  Part 6:
 date: 2025-09-17
 tags: ["Editorial", "Archival Posts / Reprints", "Language Comparison", "Performance", "Benchmarks"]
 series: ["10 Myths About Scalable Parallel Programming Languages Redux"]
-summary: "The sixth archival post from the 2012 IEEE TCSC blog series with a current reflection on it"
+summary: "The sixth archival post from the 2012 IEEE TCSC blog series, with a current reflection on it"
 authors: ["Brad Chamberlain"]
 ---
 
@@ -630,7 +630,7 @@ computer science.
 
 {{</pullquote>}}
 
-#### Wrapping Up
+### Wrapping Up
 
 Wrapping up, I want to note that while this article demonstrates that
 concise ZPL and Chapel programs _can_ outperform MPI due to the

diff --git a/content/posts/10myths-part7/index.md b/content/posts/10myths-part7/index.md
@@ -3,7 +3,7 @@ title: "10 Myths About Scalable Parallel Programming Languages (Redux),  Part 7:
 date: 2025-10-15
 tags: ["Editorial", "Archival Posts / Reprints", "Language Comparison"]
 series: ["10 Myths About Scalable Parallel Programming Languages Redux"]
-summary: "The seventh archival post from the 2012 IEEE TCSC blog series with a current reflection on it"
+summary: "The seventh archival post from the 2012 IEEE TCSC blog series, with a current reflection on it"
 authors: ["Brad Chamberlain"]
 ---
 
@@ -49,7 +49,7 @@ parts [2]({{< relref 10myths-part2
 >}}#the-original-article-reprinted), [3]({{< relref 10myths-part3
 >}}#the-original-article-reprinted), [4]({{< relref 10myths-part4
 >}}#the-original-article-reprinted), [5]({{< relref 10myths-part5
->}}#the-original-article-reprinted). and [6]({{< relref 10myths-part6
+>}}#the-original-article-reprinted), and [6]({{< relref 10myths-part6
 >}}#the-original-article-reprinted).
 
 
@@ -587,7 +587,7 @@ Chapel can support compact, readable, performant code, while also
 supporting manual overrides when desired.
 
 
-#### Wrapping Up
+### Wrapping Up
 
 That concludes this month's look at the relationship between the size
 of a language's feature set and its productivity and capabilities.