[It was] an event geared towards reconnecting in-person and collaborating on the current and future community landscape of the Elm ecosystem that surrounds the Elm core language. (excerpt from https://elm.camp)
There were some pictures taken, and some of them and other artifacts might be added to the website in the future.
I am not affiliated with the nice organizers of Elm camp who made it possible, nor am I a particularly active member of the community.
I just thought broadcasting some (incomplete) information soon after the event would be a good idea.
No need to polish too much before publishing, this is not an Elm package after all and editing the post should be easy.
I am creating this thread to not forget about all the cool things I have heard or seen. The second reason is so people who were not attending can get news from the Elm camp, and can ask questions more specific than “how was it?” and don’t have to start conversations with “tell me everything”.
Now you could for instance talk directly in this thread about topics you are interested in.
Or you could create a new discourse thread related to a session, for instance: “I want to create the next Elm camp, what should I know from the session ‘The making of Elm camp’?”
I will try my best to update this first post over the next days as new information keeps coming in. Feel free to add comments or write me direct messages if you want something in this first post changed.
I hope that in the end this first post will be useful to read a short sentence about each session from the Elm camp, and to jump to places where more information will be found. Maybe also the name of the attendee proposing/driving the topic.
There were about 40 people in Dallund Castle in total and Evan was attending Elm camp as a normal participant.
I have met him only this one time and this is what I remember and want to share:
- Evan is working on Elm full-time and is funded entirely out of his own savings since leaving noredink.
- He mentioned the upcoming https://elm.studio and his continued work on Elm on The Backend.
- And he wants to share details about his work and explorations himself when he is ready.
My personal opinion (feel free to ignore)
So far Evan has always produced high quality content and I think he wants to avoid creating too-high expectations by sharing too much, too early. So I will be patient until he thinks his new stuff is good enough to be shared and will keep enjoying what already exists and what the community is building.
All sessions were either 15 or 30 minutes long and followed the unconference-format guidelines. So most focused on direct discussions, and no one was recording or keeping minutes.
This means that the key takeaways from sessions might vary from person to person, and I would like to update this overview to reflect more opinions.
Next 5 years for Elm
Outlook as described on Elm on The Backend, and gathering ideas in small groups how to grow the impact of Elm or its community.
Elm in Business
How do companies use Elm? How do multiple teams work together? General sharing of experiences.
Further improving error messages with LLM
Worst Elm code possible (live-coding session)
A proof-of-concept debugger for understanding what is happening on the backend when working on a Lamdera app locally.
It is possible to connect https://backend-debugger.lamdera.app to any Lamdera project.
Reflecting on the last few years (non-programming-topic)
Or: “How many people moved to a farm?”
Write an elm-review rule together
Live coding following GitHub - jfmengels/elm-review: Analyzes Elm projects, to help find mistakes before your users find them. with a running commentary.
Games with Elm
Lamdera in business
More about Using Lamdera professionally
3D objects in Elm
Elm for beautiful art and music
Options for dealing with github user renaming
And discussion about the Elm package ecosystem
Live-code an elm-land app
Building a twitter clone with https://elm.land
Debugger needs and wants
Ideas for visualizing program flow.
An in-progress interpreter for Elm code, written in Elm: GitHub - miniBill/elm-interpreter
Discussions happen in the elm-interpreter channel on “Incremental Elm” Discord
TEA with LLM/AI (actor pattern)
Future Elm IDE plugins
JS mutation observer
The next version of elm-book, a tool that makes it easy to create rich documents that showcase documentation, UI components, design tokens, and more.
Browser GUI for elm --init
Ideas for scaffolding a new Elm workspace
New and exciting things in programming (outside of the Elm bubble)
UI with WebGL (instead of Html)
Showcase of an UI framework for the https://town-collab.app game. It uses WebGL and no html (hence the title) and is partly inspired by elm-ui.
Ideas for IDEs
Intellij, Language Server, elm-dev…
Getting an Elm certification
What makes a “good” Elm programmer? Certifications might be a way to fund further Elm development.
Generative art with Elm
continuation from day before
Similar to Costs/Funding in Open-Source Languages with more recent data.
The store pattern
Another look at the pattern described on 🎙 Elm Radio Episode 58: Elm Store Pattern.
Let's play games
3D objects in Elm
Similar to day before because not everyone could attend
Early wip version of an interactive code notebook for teaching, learning and experimentation. Similar to jupyter, but using elm-interpreter to evaluate Elm code.
Was already announced on slack, where jxxcarlson is also available for questions.
Internationalizing the Elm compiler error messages
It might be easier for beginners if the error messages were translated to their native language.
Also thoughts about translating the keywords, so a user might program without prior knowledge of English.
Elm + PostgREST
Showcasing different approaches and packages
3D vehicle simulation
The making of elm-camp
On finding a venue, nailing down a concept, finding sponsors and their thought process.
I try to favor publicly available links, but there are also a few links to channels on the “Incremental Elm” discord server. To join it, go to Incremental Elm Community Chat
Have fun! Or not (if you rather want to follow a being-miserable-cult than a happy-cult ).