"Code is the Easy Part" by Evan Czaplicki

Channel:elm-conf · Length:38:26 · Published:2016-09-19 · Views:42757

Watch on YouTube

Summary

Evan Czaplicki, creator of Elm, gives an elm-conf 2016 talk on the non-code side of building a language. It covers the philosophy behind Elm's development approach, including batching work and the priorities of different language communities.

Why HN recommends it

HN points people to it to understand Elm's design philosophy, such as favoring simplicity over type classes, when they question its choices.

great talk by Evan Czaplicki and his approach to Elm development — HN, 2018

Programming language design · Functional programming · Software practice, open source & careers

Subtitles (excerpt)

okay yeah so I'm Evan I'm working at no ride Inc and we've got about I I heard almost 50,000 lines of elm code there um and looking for for more people to work on it um so it's rare that I get to talk to an audience where everyone knows about Elm already so I wanted to take a chance to sort of talk about some Community stuff that isn't ever really appropriate in other places so I wanted to focus on two main questions one is what does collaboration look like in this community um and two what's next for Elm so we'll so show some stuff that's going on um and we'll sort of come back to this idea of code is the easy part you know again and again we'll see you know it writing code is important but there's all this other stuff that goes into it um and I want to start with the best advice I've ever gotten for working on this language um so when I started at Elm you know I'm just working on my own it's nice things are going well um and sort of in the periphery there are these other projects that I know about sort of languages that are like hasle compiling a JavaScript you know and more of them come into being and at some point M comes out and they're doing this uh virtual Dom rendering and it's really quick and it's

On Hacker News

Every time I hear about procrastination it reminds me about great talk by Evan Czaplicki and his approach to Elm development, actually it can be good thing ( [VIDEO] see 19:15 Batching Work). — ekoczwara, 2018-06
Here's how I see his point. He came to Elm expecting a Haskell for the web. Elm has the completely opposite philosophy of keeping things simple, even if it means extra boilerplate. I can understand OP's frustration, but if he watched a few of Evan's talks (like this one [VIDEO] ), he would realise his expectations about Elm are wrong. Also, he forgot that Elm (just like any other open source proj… — elbear, 2016-11
This mirrors my experience quite perfectly. To add another aspect: The over-management of GitHub issues is, in my experience, borderline pathological. On dozens of occasions (no exaggeration), I've experienced the following: - I notice some bug, or some missing functionality. - After dozens of searches I finally find a relevant Github issue. It's difficult to find because it's closed, in a projec… — IAmEveryone, 2020-04
I don't think the response was as simple as "No, you can't have that because I don't want to". Reading the discussion about removal of this feature on Github there seems to be a few more points made that the author alludes to: [LINK] Also, It's worth noting that Elm does have a BDFL. Evan makes the call and, as I'm sure a lot of python folks would agree, that setup means that the language is goin… — benjaminjosephw, 2016-11

Related videos