You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/posts/compiler-driven-development-elm-playground.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ No matter what I tried, `elm make` consistently exceeded the 512MB memory limit.
56
56
57
57
-**Pre-warming `elm-stuff`**: Reusing compiled dependencies between requests
58
58
-**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
60
60
-**Constraining `elm make`**: Looking for memory limit flags (spoiler: they don't exist)
61
61
62
62
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
109
109
110
110
[@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.
111
111
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:
113
113
114
114
1.**Pure frontend application** built with Elm
115
115
2.**Guida integration** for in-browser compilation
@@ -132,7 +132,7 @@ More importantly, it perfectly demonstrates compiler-driven development. Worksho
132
132
3. Experience the confidence that comes with "if it compiles, it works"
133
133
4. Understand why Elm developers love their compiler
134
134
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 🤓
0 commit comments