Skip to content

Commit 0e2d431

Browse files
committed
fix typos
1 parent 4fb9f25 commit 0e2d431

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

content/posts/compiler-driven-development-elm-playground.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ No matter what I tried, `elm make` consistently exceeded the 512MB memory limit.
5656

5757
- **Pre-warming `elm-stuff`**: Reusing compiled dependencies between requests
5858
- **Symlinking instead of copying**: Reducing disk I/O overhead
59-
- **Switching from Go to Node.js**, using the existing node-elm-compiler package: Using lighter runtime abstractions
59+
- **Switching from Go to Node.js**, using the existing node-elm-compiler package
6060
- **Constraining `elm make`**: Looking for memory limit flags (spoiler: they don't exist)
6161

6262
Nothing worked. The Elm compiler, while excellent at its job, simply requires more memory than a free hosting tier provides for even simple programs. (_Allegedly_, that is – locally I could never reproduce this high memory consumption! But how and why that is is a different post.)
@@ -109,7 +109,7 @@ Getting Guida integrated wasn't without challenges, though. Initially I hit CORS
109109

110110
[@deciojf](https://github.com/deciojf), Guida's creator, pointed me to [`elm/project-metadata-utils`](https://package.elm-lang.org/packages/elm/project-metadata-utils/latest/) for proper error message decoding. I ended up borrowing his `viewError` function.
111111

112-
With some blood, sweat, tears and greatinsights from the awesome Elm community, I finally had a working solution. The final architecture is refreshingly simple:
112+
With some blood, sweat, tears and great insights from the awesome Elm community, I finally had a working solution. The final architecture is refreshingly simple:
113113

114114
1. **Pure frontend application** built with Elm
115115
2. **Guida integration** for in-browser compilation
@@ -132,7 +132,7 @@ More importantly, it perfectly demonstrates compiler-driven development. Worksho
132132
3. Experience the confidence that comes with "if it compiles, it works"
133133
4. Understand why Elm developers love their compiler
134134

135-
The final two exercises don't work yet, because they have additional package dependencies not found in the deault `elm.json` file in Guida. But I'm quite confident I'll be able to solve that quite quickly 🤓
135+
Some of the later exercises don't work yet, because they have additional package dependencies not found in the deault `elm.json` file in Guida. But I'm quite confident I'll be able to solve that quite quickly 🤓
136136

137137
## Why This Solution is Better
138138

0 commit comments

Comments
 (0)