Introduction to Elm

with Lindsay Wardell

Elm is a functional language that compiles down to JavaScript, with “a strong emphasis on simplicity and quality tooling.” Join us on Some Antics as Lindsay Wardell helps us build some pretty familiar web applications the Elm way!

Lindsay is a full-stack developer at NoRedInk and a host of the Views on Vue podcast.

More From Lindsay

Mentioned Links


Ben: Hello, hello! Welcome back to Some Antics. Today, I am joined by the one and only Lindsay Wardell. Lindsay, welcome to the stream!

[00:00:09] Lindsay: Thank you, I'm excited to be here!

[00:00:10] Ben: I'm excited to have you! We, I guess, met through the Lunch Dev Discord, which I'll have to put a link to in the chat already. But yeah! You recently joined. We've had the pleasure of chatting a couple times. I'm super, super excited to have you on. For folks who haven't seen you around, haven't gotten to meet you yet, would you like to introduce yourself?

[00:00:35] Lindsay: Sure. My name is Lindsay Wardell. I'm in Portland, Oregon. I am an engineer at NoRedInk, which is a learning platform for middle and high schoolers to learn English and writing skills. By the way, we are hiring. And I also participate on the podcast Views on Vue and do a little bit of blogging and a little bit of talking on Twitter. That's kind of my public face. I'll also throw in I enjoy biking and I enjoy coding.

[00:01:03] Ben: And long walks along the beach and stuff like that. Yeah!

[00:01:07] But yeah! So, I'm excited to have you on. I'm excited about today's topic, which is Elm. To tell you the truth, Lindsay, I feel a little out of my wheelhouse here. It's been, you know, a while since I've learned a new language properly. Not really counting TypeScript here, because TypeScript is a superset of JavaScript. But it's been a while since I've learned any new languages like this. And so, I guess, before we really dive into what it is we're doing today, can you kind of talk to us about, like, what is Elm and why might someone use Elm over alternatives?

[00:01:46] Lindsay: Sure! So at its core, Elm is a functional programming language. The tagline on the Elm website is that it's "a delightful language for building reliable web apps." The main issue that we as JavaScript developers get into is that JavaScript is… Sorry, I'm going to put it. It has some flaws, it has some issues, and that's partly to do with why it was originally created. But when you're building a large scale application, something using React or Vue or whatever framework of the day you want to choose, you run into certain issues over and over again, things like "undefined is not a function, "cannot read null of undefined." You're not able to rely on the code that you write, even with all of the testing in place, because something could go wrong. And something is data coming in from an API, say that it could be a user gave some input that you weren't expecting. It's possible to get into impossible situations. Just that much easier in JavaScript.

[00:02:52] Where Elm really shines is that it is a language that is designed for building reliable web apps from the start. So what some of the guarantees with Elm is you will almost never see a runtime exception. If your code is able to compile and it is able to run, it will not crash on the client side. You will not have an "undefined is not a function." Elm actually doesn't even have a concept of undefined or null.

[00:03:17] Ben: Whoa!

[00:03:18] Lindsay: Some of the other guarantees are that when you're making an HTTP request, for example, something very common in JavaScript apps, that data that comes back has to be parsed from a JSON object, which Elm doesn't even really recognize JSON as a type. It's just when you get an HTTP request, you can say you're expecting JSON and then parse it into the data type that you're expecting within Elm. So if you don't get the JSON back that you're expecting, it will go into an error state and you'll have to handle that error, saying "The server returned something wrong. I'm sorry. I can't do that." Rather than, even if you're using TypeScript, you can say that the — let's say we're using fetch — await fetch(), and then you do a res.json() on it. You can type that in TypeScript and say "I expect this data to be in this type structure" and start acting on it. But there's nothing actually guaranteeing that that data is that type.

[00:04:14] Ben: Mm!

[00:04:14] Lindsay: So that's where some of Elm's guarantees come in, that the data you're getting is actually what you expect. And rather than it being a framework or library on top of JavaScript, it's a full language, so there's complete control over the ecosystem. There's complete control over how the language is structured, how the code is written, so that at the end of the day, you have an application that is as reliable as you expect it to be.

[00:04:42] Ben: Gotcha, and I think that's really interesting that you call it out in comparison to TypeScript, because my experience with TypeScript — like, first of all, TypeScript has, I think, more escape hatches than the marketing would lead you to believe. But, like, TypeScript also has kind of this constraint that they've started with, which is that they are a superset of JavaScript so ultimately, everything is kind of bolted onto JavaScript syntax, right? It's JavaScript plus the closest way that TypeScript could get to what it is they want it to get to in that syntax. Whereas Elm is a blank slate, right?

[00:05:21] Lindsay: Right. So Elm does compile to JavaScript. Its compiler is written in Haskell and turns the Elm code into JavaScript, but it's not reliant on how JavaScript does things or how JavaScript allows for any data to be any type at any time. And you're right, TypeScript has a lot of escape hatches. There's the any type, there's the unknown type, and there's the fact that the web APIs… sometimes you just can't control what comes out of them.

[00:05:49] Ben: Mm!

[00:05:49] Lindsay: Fetch is a good example. JSON.parse() is another example. You just can't anticipate what's going to happen. Whereas with Elm, because it is a compiled language, you're able to do that static analysis of "all of my data is the type that I am expecting and nothing is going to happen that I don't anticipate." Obviously with all of this, business logic can still be wrong. Elm doesn't suddenly make you a 10× developer, whatever that means. But you have some strong guarantees and reassurances as you're writing the code that everything works as expected.

[00:06:26] Ben: Gotcha. Okay! Yeah, so I'd love to start diving into what we're doing. Is there any, like, more you wanted to say about Elm before we start kind of showing some code and diving in?

[00:06:39] Lindsay: No, let's dive into the code! We'll talk about it as we go.

[00:06:42] Ben: Awesome. So we are now looking at my screen. I am showing Lindsay's Twitter. Y'all, go follow her on Twitter. Go show her the Some Antics love. She is @lindsaykwardell on Twitter.

[00:06:58] Yeah, so you sent me ahead of time, you've got this template that we're going to be using. Can you kind of talk about this template a bit?

[00:07:06] Lindsay: Yeah, so coming from the Vue ecosystem, I am a big fan of the Vite developer tool. And one of the nice things about how Elm is written is there's integrations into all of these different bundlers. So there's one for Webpack, there's one for Rollup. It's actually built into Parcel, so if you're using Parcel for your bundling, you can just import Elm files automatically.

[00:07:28] Ben: Oh, dang!

[00:07:29] Lindsay: But I really like Vite, so I put this template together as a baseline. If you wanted to start an Elm application using Vite and get the benefits of the Vite ecosystem, you can just start with this template and start writing Elm code pretty easily.

[00:07:44] Some of the nice features of the template itself is the Elm plugin provides hot module reload. So if you're working on an Elm module, it will try to hot reload if it can. Obviously, if it can't, it'll just refresh the page. Also comes with some built-in examples of tests using the elm-test library, and uses the GitHub workflow to enable that whenever you do a commit, so it will run the tests for you, which is kind of fun!

[00:08:13] Ben: Okay!

[00:08:14] Lindsay: Yeah. I think that's the basics of it. I love Vite. You should go check out Vite if you're not using it.

[00:08:18] Ben: We had an episode a while back with Anthony, who's in the chat today. Let me get a link to that in the chat there.

[00:08:30] Yeah, so we're going to go ahead and use this. I'll just use this handy green "Use this template" button here, and we're going to find my SomeAnticsDev. Should I call this anything in particular or is, like, "introduction-to-elm" good enough, or…?

[00:08:47] Lindsay: It should be fine.

[00:08:48] Ben: Cool.

[00:08:49] Lindsay: I don't think there's anything specific we need.

[00:08:51] Ben: Alright. And let's go ahead and make that public. And do I need to include all branches, or nah?

[00:08:58] Lindsay: Nah.

[00:08:59] Ben: Cool. Alright. In that case, here's already a link to our repo that we'll be playing with, so after all of this is done, you'll be able to find the source code in here! Very cool. And let me go ahead and clone this down.

[00:09:19] Lindsay: Sounds good. While you're doing that, I'll make one more comment. The template also includes a package from npm called elm-tooling. Because Elm is its own language, typically you would have to install Elm itself onto your machine. elm-tooling does that for you, so it will bring the Elm language itself and a couple of different tools—

[00:09:43] Ben: Ohh! Okay.

[00:09:43] Lindsay: —so that everything is in place for your repository, which is really nice.

[00:09:47] Ben: Interesting! Because, like, if you're writing Python code, you have to install the, like, Python binary and everything like that. This is just, it's part of the repo configuration, is it will pull…?

[00:09:58] Lindsay: Yep.

[00:09:58] Ben: Wow, interesting! Okay. Very, very neat!

[00:10:04] So I've got the code, and so should I…? I'm just gonna peek at the package.json. That seems like a good place to start. Ooh! Actually, I probably should not have dismissed that, but okay!

[00:10:18] Lindsay: That's okay, we can get back to it.

[00:10:20] Ben: And so I see you've got "postinstall". You've got "dev", "prebuild", "build", "serve", and "test". Okay, so I'm just gonna install my dependencies?

[00:10:30] Lindsay: Yup.

[00:10:36] And we'll see here, because it's in the post-install, once everything is in place, elm-tooling will do its thing and it'll bring elm, elm-format. elm-json, and elm-test-rs. elm itself is the Elm language. elm-format is… think of it as Prettier.

[00:10:52] Ben: Okay.

[00:10:53] Lindsay: Unlike in JavaScript where you can kind of debate what styling and formatting is best, whether you should use semicolons or not or something like that, Elm has an official style guide.

[00:11:02] Ben: Mm!

[00:11:03] Lindsay: And elm-format just enforces it, which is nice.

[00:11:06] Ben: Very cool.

[00:11:06] Lindsay: elm-json, we don't need to worry about. It's for updating dependencies and installing dependencies. And elm-test-rs is the Elm test runner written in Rust.

[00:11:15] Ben: Got it. Okay! Very neat!

[00:11:20] Lindsay: So, yeah. That is it as far as installing. We should just be able to run npm run dev and get our dev server up and running.

[00:11:28] Ben: Let's do it!

[00:11:37] And… localhost:3000. I have to go manually open this in my browser of choice because otherwise it will pop up off screen. Something is hogging my memory resources. It couldn't be any piece of the whole streaming setup. Couldn't be any of that.

[00:11:55] Lindsay: No, no.

[00:11:59] Ben: There we go! Okay!

[00:12:00] Lindsay: And there you go!

[00:12:00] Ben: Nice! By the way, lovely work on the logo.

[00:12:04] Lindsay: Elm has a great logo. One of the nice things is the community will take that logo and convert it into different shapes—

[00:12:11] Ben: Okay…?

[00:12:11] Lindsay: —for different things. So, like, there's an Elm Weekly newsletter that has turned it into the shape of a heart!

[00:12:17] Ben: Nice!

[00:12:18] Lindsay: Fun things like that.

[00:12:20] Ben: You've just gone in and basically used the Vite color schemes. I love it. Let's see, does this work?

[00:12:27] Lindsay: So this is all being rendered by Elm. So the count is just incrementing, and it shows you how we can edit the Main.elm file to auto-refresh. Before you move on, if you see in the bottom right corner, there's a counter that's been ticking up. Click on that.

[00:12:43] Ben: Okay! Whoa, what's this?

[00:12:46] Lindsay: Just like with something like Redux or VueX, Elm allows for time-traveling debugging.

[00:12:52] Ben: Okay, okay!

[00:12:53] Lindsay: So we can go backward and forward in time and see what the state of our application is in and what caused it to change. So in this case, we're sending a message of "Increment" to our app, which is then incrementing the model by one number at a time.

[00:13:09] Ben: Wow. That's just all built into Elm, you said?

[00:13:12] Lindsay: It is built into the template.

[00:13:15] Ben: Oh, okay.

[00:13:16] Lindsay: The Vite plugin for Elm brings this in as long as we're in development mode.

[00:13:20] Ben: Okay.

[00:13:21] Lindsay: But it's available across different development models, so if you're using Webpack. I think if you're using Parcel, it's there, too. There's lots of ways to get this. But it's one of the really nice features if you're trying to figure out what's going on, what state is my application in, things like that.

[00:13:37] Ben: Oof. Someone's asking about our sound. We were trying to debug the sound ahead of time. Let us know if that's an improvement at all. We've been having sound issues a bit. Sorry, I don't know if this helps. If that's made it worse, let me know. But yeah, I don't know that we're going to get much better in real time.

[00:14:03] Someone has mentioned, hey, we should click the logo on the Elmlang site. Whoa!

[00:14:09] Lindsay: Oh, yeah, yeah, yeah. It rearranges.

[00:14:10] Ben: Nice, it's very cute.

[00:14:13] szinka, please let us know if that helped at all. Yeah, okay. Cool.

[00:14:23] Lindsay: I'll just keep talking to validate that.

[00:14:26] Ben: Yeah, that would be a good call.

[00:14:27] Lindsay: So yeah, so this is a basic template. Let's go to the code. Let's leave the server running so we can see things happen live, but let's stick in the code for a little bit. In the template itself, if you open up src/, you'll see three different files. We've got a HelloWorld, a Main.elm, and a Message.elm. We're actually going to delete the HelloWorld and Message once we get started here.

[00:14:52] Ben: Okay!

[00:14:52] Lindsay: I just wanted to look at them real quick as examples. So here is the HelloWorld module.

[00:15:01] Ben: I probably should have installed that Elm plugin.

[00:15:03] Lindsay: Oh, yeah, we need the extension!

[00:15:04] Ben: Yeah! Let's do that.

[00:15:05] Lindsay: If you type in "Elm," it's the second extension, not the first one.

[00:15:12] Ben: This one that looks like it's got the, like, little wrench?

[00:15:16] Lindsay: Yes.

[00:15:16] Ben: Okay.

[00:15:17] Lindsay: So that is made as part of elm-tooling.

[00:15:20] Ben: Mmmm.

[00:15:21] Lindsay: And that will integrate all of the lovely things that we need, including some code highlighting.

[00:15:28] Ben: Okay! It's installed.

[00:15:32] Lindsay: Woo!

[00:15:33] Ben: And something here is thinking hard about what it wants to do for us. Let me shut down Discord, see if that helps at all. Alright. Wow! Something's chuggin'! Shut down Opera as well, I guess? See if that helps.

[00:16:01] TechnoTone, thank you so much for the follow. Appreciate having you.

[00:16:04] Huh, this is… Okay, I'm sure that this will pop in eventually at some opportune time.

[00:16:16] Lindsay: Yes.

[00:16:17] Ben: But in the meantime, can we… like, what is going on here?

[00:16:22] Lindsay: So like with many other languages — hey, the code formatting! Like with many other languages, you have at the top, first you're declaring what this file is. We're saying module HelloWorld exposing (helloWorld). So if you're thinking like an object or a class, helloWorld is our public method, is what that is saying there. And the name of this file is HelloWorld, so it's module HelloWorld.

[00:16:49] We then have a number of imports, which we will come back to later, but just like with JavaScript or Python or something, if you want to import from another file, this is the syntax you would use for that.

[00:16:59] And then helloWorld itself, the function… we'll get a little more into this, but basically what it's doing here is taking in our model, which is just a number, and then returning some HTML. So with Elm, everything is a function, and that's something to important to keep in mind. So as we're generating HTML, we're calling a function — in this case, div — that takes two arguments. One is a list of attributes and the other is a list of more HTML.

[00:17:30] Ben: Okay, so we're not providing any attributes at the moment.

[00:17:33] Lindsay: Correct. But because of Elm's strong type system, we always need to provide the argument, even if it's going to be empty.

[00:17:41] Ben: Okay.

[00:17:42] Lindsay: And then we provide the list of HTML. So in this case, it's that h1 and then a couple of paragraphs and a button that increments.

[00:17:49] Ben: Okay!

[00:17:51] Lindsay: So just some straightforward stuff. We'll be writing something similar to this in just a bit. For now, though, let's jump over to our Main.elm file.

[00:18:02] Ben: Yeah, just a second. I think I might actually be able to help with some of the audio stuff. Do let me know if that helped at all. Yeah. Properties, let's see… Alright, yeah. Sorry about that. Anyways, go where?

[00:18:27] Lindsay: Sorry, I was just going to poke my microphone, too .Let me know if that helps.

[00:18:32] Ben: I think whatever audio stuff is going on is on my end, unfortunately, and that makes it a little difficult to debug. Because again, I hear you just fine. It's however audio is being passed around on the Mac.

[00:18:46] Lindsay: Gotcha.

[00:18:47] Ben: Yeah.

[00:18:47] Lindsay: Okay. So at this point, we're going to go to Main.elm, and Main.elm at the moment is pretty straightforward. We have a main function, we have an update function, and a view function. We're actually going to delete everything here and just start from scratch. So go ahead and just delete it all.

[00:19:03] The first thing we need to do, like we looked at in the HelloWorld file, is we need to declare this module. So we're going to say, just like it says module HelloWorld exposing (helloWorld), we're going to say in this case module Main, because that's the name of the file.

[00:19:18] Ben: Is that capital?

[00:19:18] Lindsay: Capital M.

[00:19:19] Ben: Okay.

[00:19:21] Lindsay: exposing… and then we're doing parentheses, and just say main, and we'll declare that function in just a moment.

[00:19:30] Ben: Okay. So this, I would say is — Ooh, comments are apparently double hyphens. Interesting.

[00:19:37] Lindsay: Yes.

[00:19:38] Ben: So this is equivalent to probably, like, module.exports = main; where main is some function, or, like, export default main;, right?

[00:19:52] Lindsay: It's more like the first one.

[00:19:54] Ben: Okay.

[00:19:56] Lindsay: So you can also think of it as either module.exports or export function main, and then you declare it or something like that.

[00:20:04] Ben: Yeah. Okay!

[00:20:06] Lindsay: So the next thing we need to do, because as we're writing a web application, we need to generate some HTML. So at this point we need to import Html.

[00:20:16] Ben: Is that lowercase like this?

[00:20:19] Lindsay: With a capital H in this case. So, all Elm modules start with a capital letter.

[00:20:25] Ben: Okay.

[00:20:25] Lindsay: And that's all we're gonna do right now. And now, let's declare our main function. So go down a couple more lines. Just type main =. And then Html.text, using a capital H. And just say "Hello World" after that. Space, quotes, "Hello World." Sorry.

[00:20:49] Ben: Mm. So it seems like Elm has done away with the notion of just parentheses where you would expect parentheses.

[00:21:00] Lindsay: Yes. So there are still parentheses when you need some sort of order of operations, and we'll get to a point where that matters, but in general you don't need to do that for arguments for a function.

[00:21:14] So in this case, before we go back to the browser, what we're doing here is declaring a Main module, which exposes the function called main. We are importing the Html module so that we can do stuff with HTML. And then we are saying that main function is equal to Html.text, which itself is a function which takes a string, and then we provide the string "Hello World." So if we go back to the browser now, we will see that what we have done here is render "Hello World" to the screen!

[00:21:47] Ben: Nice! And this is just a… like, if I were to inspect this, I'm sure it's a text fragment, is what's going on there. That's what Html.text is, I'm guessing.

[00:21:56] Lindsay: I believe so, yes.

[00:21:58] Ben: Looks like there's a… well, this is probably the root, I'm guessing, or part of it.

[00:22:03] Lindsay: Right, yes.

[00:22:04] Ben: But this is what we've created.

[00:22:06] Lindsay: Cool. Great. So, hooray! We've written an element! Congratulations. So now we're going to play around a little bit more. Let's go back to the code.

[00:22:20] Ben: My swipe was incorrect. I did not swipe correctly. And for that, I was punished. Alright.

[00:22:30] Lindsay: So, first thing we're going to do is explore functions a little more and play around with how we can do things with strings. So like I said, that Html.text, that is a function. And in this case, the argument to it is a string, which we're providing as "Hello World." And it returns actual HTML for the Elm… words… for the Elm virtual DOM to render out to the browser. Similar to React and Vue, Elm does use a virtual DOM for how it works. It's very similar to how React handles things. So if the state changes, it then does a rerender of the app.

[00:23:12] Ben: Okay.

[00:23:13] Lindsay: And similar to React, where React has useMemo or something like that, Elm has ways to handle preventing stuff from rerendering if we don't need it to. We're not going to worry about that right now. We're not building anything that complex.

[00:23:27] So the next thing we're going to do is, let's just create a new function to handle our greet needs. So let's call it greet, and you can just say greet =. And if you just say "Hello World." Let's just start there. So if you replace "Hello World" in our main function with greet, we will see what that does.

[00:23:51] Ben: Like this?

[00:23:52] Lindsay: Just like that.

[00:23:53] Ben: Okay?

[00:23:55] Lindsay: We can go back to the browser. It's not going to look any different. It still says "Hello World." What we are doing is, greet is a function, so rather than thinking of everything as, like, variables…

[00:24:07] There you go.

[00:24:08] Ben: Okay!

[00:24:10] Lindsay: Instead of thinking of things as variables, it's important to think of things as functions. So greet is a function that returns a string, and that's all it does. main is a function that returns some HTML, and that's all it does.

[00:24:22] Well, you can add arguments to these functions though, so let's do that with greet. Instead of… Thinking in JavaScript terms, what we would normally do is write some parentheses and then name some variables inside of the parentheses, right? In Elm, we don't need to do that. So instead of parentheses and then arguments, you just put the names of the arguments after the function name, before the equals. So if we wanted to say greet and then have a variable of name, you just say, greet name =

[00:24:56] Ben: greet name = like this, you said?

[00:25:00] Lindsay: Just like that.

[00:25:01] Ben: Okay.

[00:25:02] Lindsay: And then instead of "Hello Chat," we need to say "Hello {name}," so we need to do some concatenation here. It's similar to JavaScript in that you can concatenate strings as one would hope. Unlike JavaScript though, you do need two plus signs. But before you add it, I want to show off one of the cool features of Elm. Can you go to the terminal? No, have the + name there. That was good.

[00:25:28] Ben: Okay, okay!

[00:25:30] Lindsay: I just want to show off one of the features of Elm, which is the compiler being super friendly.

[00:25:34] Ben: Boom! Okay, it didn't go to the terminal but to the browser. That's even better.

[00:25:38] Lindsay: That works too. That's the plugin for Vite helping us out.

[00:25:42] Ben: Mm!

[00:25:43] Lindsay: So it's providing us with some context here. "The 1st argument to text is not what I expect. This greet value is something, but text needs the 1st argument to be a String." And then the second one is where we just changed something, so greet name = "Hello " + name. "The (+) operator only works with integers and float values. Hint: Switch to the (++) operator to append strings!"

[00:26:06] Ben: Niiiice!

[00:26:07] Lindsay: So this is one of the really nice features of the Elm compiler is it's trying its best to be super helpful and friendly. It's not just going to return "Invalid syntax" and throw you some errors that you have to go look up on Stack Overflow or something. It's going to do its best to explain what's going on. So we can see the two errors that we were having there. One is we're not concatenating with the concatenate string method. The other is — now we can see it even clearer — "This greet value is a: String to String." So what it's saying there is with the type system, it's expecting a string and it returns a string, but text needs the first argument to be just a string. So what we need to do is provide an argument to greet just like we declared in its declaration. So we can say Html.text greet, and then we can say "Chat" or our name or "Bob."

[00:27:03] Ben: No. So that's not the syntax.

[00:27:07] Lindsay: No, that is it actually, but because Html.text expects only one argument.

[00:27:11] Ben: Ohhh!

[00:27:12] Lindsay: We need to wrap greet "Chat" in parentheses.

[00:27:15] Ben: Okay, treating it as, like, a singular expression that can be resolved.

[00:27:20] Lindsay: Right.

[00:27:20] Ben: Heyyyyyy! We're back. We're back. I can go in and I can change this to say, like, "Hello Lindsay," and that works. Also, that is reloading very quickly. Like, it's loading much faster than I can actually switch between windows.

[00:27:36] Lindsay: Yep. Yeah, it's pretty fast. And part of that is also that Vite is just amazing to work with. But yeah, the Elm compiler is pretty quick, all things considered.

[00:27:50] So let's dive back into the code. I want to show off one more thing while we're talking about strings, and that is a cool concept in functional programming of partial application. So let's update our greet function to take two arguments of firstName and lastName.

[00:28:10] Ben: Is it like this? Like, just space-separated?

[00:28:13] Lindsay: Just like that.

[00:28:14] Ben: Okay.

[00:28:14] Lindsay: Yup. And then let's update to do concatenation on both of those.

[00:28:22] Ben: It's not automatically going to add spaces, right?

[00:28:25] Lindsay: It is not.

[00:28:25] Ben: Okay.

[00:28:26] Lindsay: So you'll have to do that manually. Cool.

[00:28:31] So at this point, our greet function is incorrect in our main function, but let's not worry about that right now. Let's create another function underneath. And we can call this one, I don't know, greetLindsay. And have it take a lastName and have it equal greet "Lindsay".

[00:29:01] Ben: Okay…?

[00:29:03] Lindsay: So what we have done now — don't switch to anything — but what we have done now is, greet the function takes two arguments, firstName and lastName, and by saying, greet "Lindsay", we have created a function (which is called greetLindsay) that only takes ONE argument and then finishes the function call.

[00:29:25] Ben: Mm.

[00:29:26] Lindsay: So if we do something like in the main function, change that to greetLindsay instead of greet, and then put my last name "Wardell."

[00:29:40] Ben: In the JavaScript space, I believe…

[00:29:43] Lindsay: There is one piece I'm forgetting, I think. We do need to use that last name. So greet "Lindsay" lastName.

[00:29:51] Ben: Oh, yeah, yeah, okay, yep.

[00:29:53] Lindsay: Sorry, that was my bad. Not concatenating, just passing it in as an argument.

[00:30:01] Ben: Ah, right, okay.

[00:30:02] Lindsay: No, no, no, sorry. We don't need it. Ahh, I'm forgetting things. My apologies to everyone watching. We don't need lastName here because we're doing the partial application, so we can delete lastName altogether from the second greet "Lindsay".

[00:30:16] Ben: Okay, so like this.

[00:30:18] Lindsay: Just like that, just like that.

[00:30:20] Ben: Mm!

[00:30:20] Lindsay: And if we go back to our browser, we should say "Hello Lindsay Wardell."

[00:30:25] Ben: Okay. Oh! Oh, nice, okay. Very cool.

[00:30:28] Lindsay: I was messing up. My bad.

[00:30:30] Ben: In an immediate breach of naming here, if I had replaced this with… yeah. Okay, cool. So I believe in JavaScript spaces, first of all, it's not nearly as easy to do partial application, but I believe this is what in JavaScript spaces we might call currying. Wow.

[00:30:50] Lindsay: Yes.

[00:30:50] Ben: That is hard to say. Curr-y-ing. There we go. Currying.

[00:30:53] Lindsay: Yeah, same basic idea.

[00:30:55] Ben: Just, I think this is far cleaner of a way to do it.

[00:31:00] Lindsay: Yeah. And so you can stack this. If you have, like, a complex function that you want to pass down to lower in your function tree, then you can prepare it by passing in most of its arguments but not the last one, and then pass it down—

[00:31:16] Ben: Mmm.

[00:31:17] Lindsay: —rather than having to provide everything upfront or pass an event all the way to the top that's then called at the top level of your application. So it can make some function calls a lot simpler when you're working in submodules, for example.

[00:31:30] Ben: Gotcha. And this is nice, too, cause like, yeah, it allows you, like, a way to provide, I think, a smoother API where for instance, you could have a lot going on, maybe a lot of possible configurations getting passed around, but then there's, like, the version of the API that's, like, the sensible defaults that you would need in most cases. So you could partially apply most of those defaults, and then the one configuration that's mandatory is, you know, the function that you actually end up using. You still have all of those other functions with all the other configurations, but there's also just the smoother API. I'm thinking of, basically, this as a replacement to everything that Redux is doing with like… Redux has its connect API, but that's actually, like, a smooth layer over connectAdvanced which has, like, so many more arguments. Like, this is a way to do that, basically.

[00:32:25] Lindsay: Yeah. And actually, if you dig into the history of Redux, I believe Redux was inspired by Elm.

[00:32:32] Ben: Oh, dang! Oh, dang.

[00:32:34] Lindsay: So there is some lineage there between Redux and Elm. And the other Flux libraries, honestly. Kind of interesting.

[00:32:46] So let's move on to our next piece. I want to talk a little bit about how we would do things to strings. So for example, in JavaScript, if you are wanting to call… I can't think of a good example off the top of my head. If you're wanting to — So, let's do numbers instead actually.

[00:33:10] So first off, numbers in Elm, if you're wanting to do basic addition, subtraction, and stuff, that works exactly as you would expect. So if you want to do 1 + 1, it will return 2. 1 - 1 would return 0. Things like that. The main difference in Elm to JavaScript is that Elm has two different number types. There is an integer and there is a float. So if you are doing division, for example, then you have to think about, "Am I using integers or am I using floats? What do I need to convert from an integer to a float or vice versa?"

[00:33:40] Ben: Mhmm.

[00:33:42] Lindsay: Something to keep in mind. We're not going to be actually doing that kind of math. I just wanted to explain it real quick.

[00:33:48] Ben: Okay.

[00:33:48] Lindsay: Let's handle some numbers here, for example, with our greet function. Or we could… yeah. Yeah, let's use the greet function. So let's change it back to just greet name and simplify things. We don't need the whole thing.

[00:34:06] And, yeah. Perfect. But let's add a second argument of… I don't know, let's do favoriteNumber.

[00:34:19] So at this point, let's do ++, or concatenation, and then some parentheses and go to a new line. So we're going to do an if statement and we're going to just show off a little bit with numbers. So… yeah. So if favoriteNumber is equal to 17, which is my favorite number.

[00:34:51] Ben: Okay, is that double equals? Is that what's going on?

[00:34:53] Lindsay: Double equals, yeah.

[00:34:54] Ben: Okay, okay.

[00:34:56] Lindsay: So at this point, rather than where JavaScript would break into curly brackets, we just say then. So if this then do something. And we can say in quotes… because we're returning a string here, because we're concatenating… say something like "That's my favorite number, too." You know, whatever's comfortable.

[00:35:25] Ben: Okay?

[00:35:25] Lindsay: Cool.

[00:35:27] Ben: So just like this?

[00:35:29] Lindsay: Just like that. And let's go look at the browser real quick.

[00:35:33] Ben: And it's gonna… yeah, 'cause we haven't actually passed a number.

[00:35:38] Lindsay: Oh, it's also complaining about the tab.

[00:35:40] Ben: Ohh.

[00:35:40] Lindsay: So, this is another piece about the Elm formatting. Is it expects four spaces. And actually, because you have the Elm tooling installed, if you do save, it might do an auto-format.

[00:35:55] Ben: I think I actually disabled that in my VS Code.

[00:35:59] Lindsay: Oh, okay, then let's not worry about it right now.

[00:36:00] Ben: Okay. Just a thing to keep in mind.

[00:36:03] Lindsay: Yes. So let's jump back. Cool.

[00:36:09] "I was expecting to see an else branch after this. I know what to do when the condition is True, but what happens when it is False? Add an else branch to handle that scenario!" So this is one of those guarantees about a reliable web app. If Elm sees that you're doing an if statement, the other side of that if statement has to return something too, and it has to be the same type. So in this case, because if the favorite number is 17, then we're returning a string, we also have to return a string with the else branch. So let's go back and just add something like else "That's a cool number" or something like that.

[00:36:45] Ben: Can I do that on a new line like this?

[00:36:47] Lindsay: You can do that on a new line, yeah.

[00:36:58] Ben: Oh, god. That's a habit I would have to break.

[00:37:03] Lindsay: Oh, yeah.

[00:37:05] Ben: Unfinished parentheses…?

[00:37:08] Lindsay: It might just be that the paren is not at the same tab.

[00:37:14] No, the new one. Push that in by four spaces.

[00:37:20] Ben: Oh… OH! Oh, that's… Okay, that was not how I was expecting… God, okay. And finally…

[00:37:32] Lindsay: And now our greet function is not getting what it expects anymore, so pass in whatever number you'd like.

[00:37:38] Ben: greet 14. "Hello, Wardell. That's a pretty cool number, friend." And if I go back and say with 17, that's Elm's favorite number, too.

[00:37:51] Lindsay: Woo!

[00:37:54] Ben: Alright!

[00:37:54] Lindsay: So yeah, so that's how an if statement works and that's how you can do basic things with numbers. It's fairly similar to JavaScript — plus, minus, multiplication, subtraction, comparisons. I can't think of an example where things are weird between the two, except that integers and floats are a thing as opposed to just JavaScript numbers.

[00:38:16] Ben: Mhmm.

[00:38:19] Lindsay: So let's do one more fun thing here and let's look at lists. So in our HelloWorld file… we don't need to go there, but we saw that div, for example, the div function, took two arguments of lists. So let's do that here.

[00:38:40] Ben: Yeah. Okay.

[00:38:43] Lindsay: So we're going to do the same thing and…

[00:38:46] Ben: Up here?

[00:38:46] Lindsay: …instead of returning Html.text as the thing, we're going to do Html.div. And the first argument is the list of attributes, which we're not doing anything with. And then the second list would be our actual content.

[00:39:06] Ben: Okay?

[00:39:08] Lindsay: So let's just do the same thing that we were doing. Yeah. We do need to return text still. So Html.text.

[00:39:15] Ben: Okay, and that's just like this.

[00:39:18] Lindsay: Just like that.

[00:39:19] Ben: And then put in here, let's say greet, we'll say "Lindsay," then 12.

[00:39:27] Lindsay: Great. "Cannot find the end of this list." Oh, I think it's the last bracket is not indented the same.

[00:39:36] Ben: That is… a choice.

[00:39:40] Lindsay: It is a choice. And this is where elm-format comes in to help.

[00:39:49] Ben: Yeah. I need to turn that on, I think. Command-Shift-P, and then "Format on save." No? Okay.

[00:40:05] Lindsay: You might be able to just right-click on the file and do format, too. Yeah, in there.

[00:40:11] Ben: I think it might be having issues 'cause we installed this live instead of, like…

[00:40:16] Lindsay: Ohhh.

[00:40:16] Ben: …restarting the editor, but okay! It's fine. I will live with it, but I'm sure the experiences for default VS Code when you've got this all installed and it's settled, I'm sure that's — oh, Command-COMMA.

[00:40:30] Lindsay: Aha.

[00:40:30] Ben: Yeah, there we go. Format on save. Thank you, OneMoreLayer. You are a hero.

[00:40:38] Lindsay: Thank you!

[00:40:39] Ben: Yeah, let's put that to the test.

[00:40:46] Lindsay: Yes.

[00:40:48] Ben: No. Okay, interesting.

[00:40:50] Lindsay: Oh, no!

[00:40:51] Ben: Let me just restart Code and meanwhile, you can talk as to what the next piece of the stream is.

[00:40:58] Lindsay: Sure. So the next thing we're going to do is we're going to make a list of records. So I want to get through the main types of Elm compared to JavaScript stuff. So we've looked at lists, we've looked at strings, we've looked at numbers. We've looked a little bit at booleans, in that we did an if statement. But let's explore what…

[00:41:27] Ben: Yeah, I think that's fine.

[00:41:29] Lindsay: That's fine. That's fine. But the last thing we need to look at to match what we know with JavaScript is a record. And a record is just like a JavaScript object—

[00:41:43] Ben: Okay.

[00:41:43] Lindsay: —except… this is something to keep in mind for everything we've been doing. All values are immutable in Elm, so there is no mutable state.

[00:41:53] Ben: Okay.

[00:41:54] Lindsay: So if we're going to create a record, we're not going to be changing it anytime.

[00:41:57] Ben: Mm.

[00:41:57] Lindsay: So we can update it and get a new record, but we can't update the existing one.

[00:42:02] Ben: Gotcha.

[00:42:04] Lindsay: So let's create a new function called people, and people is going to return a list of people! So just people =, and then square brackets. And within those square brackets, we are going to put two people. So let's just put you and me, Ben.

[00:42:29] Ben: Okay.

[00:42:29] Lindsay: So first we'll do curly brackets. And we'll say name for the person's name. name = in this case, instead of a colon. name = "Lindsay". In quotes. And comma. And then let's just say number = 17.

[00:42:55] Ben: And then am I doing this right?

[00:42:57] Lindsay: Yep, you're doing that right.

[00:42:58] Ben: Like, this feels fairly, fairly JSON with equals instead of colons, but okay. favoriteNumber… or I guess it's just going to be number in this case.

[00:43:09] Lindsay: Yeah, I was just simplifying.

[00:43:11] Ben: I'll make that 14 because why not?

[00:43:14] Lindsay: Why not? Okay, so what we're going to do at this point is render this list of people out instead of just the Html.text. We're going to use this list of people and use a map function to turn it into what we want.

[00:43:31] Ben: Okay!

[00:43:32] Lindsay: This is going to feel very familiar if you've used React or used the map function in JavaScript before. The main difference is, unlike in JavaScript, because Elm is not object-oriented, it doesn't have inheritance. It doesn't have prototypes or anything. We can't just call or something like that. We need to call a list function,

[00:43:55] Ben: Okay.

[00:43:56] Lindsay: So in our main function, delete the second array altogether, or the second list. And in parentheses, call List — capital L — .map. And do another set of parentheses. And in this case, we're going to do — making sure I'm saying it right — a backslash. So this is how we do a lambda function in Elm. So just say \person.

[00:44:33] Ben: Did I choose the right slash? I can never remember which slash is back.

[00:44:36] Lindsay: You did.

[00:44:37] Ben: Okay.

[00:44:37] Lindsay: I don't know if I said the right one, but that's the one I meant.

[00:44:40] Ben: Okay!

[00:44:40] Lindsay: So we're on the same page.

[00:44:42] Ben: Cool.

[00:44:42] Lindsay: Then we're going to do a small arrow. So JavaScript uses equals and bracket. We're going to do that, yep. Space. And then we can call our Html.text, just like we've been doing. And then… one more set of parentheses, and then we'll call greet person.number. And then the last thing we need inside the yellow brackets — the yellow parentheses — is our list of people.

[00:45:22] Ben: Okay.

[00:45:26] Lindsay: So what are we doing here? We have a function, people, which is returning a list with two items, Lindsay and Ben. And then we are using to map over that and return a list of HTML. We're taking person as an argument and then passing its name and number in as arguments to greet. So on the screen now, we should see two hellos.

[00:45:51] Ben: It's gross, it's not formatted, but it works!

[00:45:55] [Lindsay laughs]

[00:45:58] Alright!

[00:45:58] Lindsay: And the goal here was more to see how functions on lists work. There's a whole bunch of these kinds of functions. So if we wanted to convert a number to a string, for example, we could call String.fromInt or String.fromFloat.

[00:46:15] Ben: Mmm.

[00:46:15] Lindsay: You can do the same thing the other direction, String.toInt or String.toFloat. There's, there's List.sortBy, there's List.reverse. So that's some of the fun stuff that we can do with this. And if we wanted to format this better, we could replace the Html.text with actually returning a <div> that returned text to get them on different layers.

[00:46:38] Ben: Are any HTML elements valid? Like, can I do a paragraph tag?

[00:46:44] Lindsay: You can! It does still need to hold text.

[00:46:47] Ben: Oh.

[00:46:48] Lindsay: So if you're going to return a string to the browser, it needs to have Html.text.

[00:46:54] Ben: Okay, so how would I wrap this in a <div> then? Or a paragraph. It would be like this, and then…

[00:47:00] Lindsay: Html.p.

[00:47:00] Ben: And then another set of parentheses?

[00:47:07] Lindsay: So at first you would need the first set of square brackets for the list of attributes.

[00:47:13] Ben: Aah.

[00:47:14] Lindsay: And then you would need a second list or, yeah, a second set of square brackets for the content instead of parentheses.

[00:47:22] Ben: Interesting. And then I feel like I've gotten the nesting wrong here, but…

[00:47:28] Lindsay: I think it is, yeah. Put a parenthesis outside the square, yeah.

[00:47:33] Ben: There we go.

[00:47:34] Lindsay: That should work.

[00:47:36] Ben: Hey! Pretty sharp.

[00:47:39] Lindsay: Nice. So one last thing I want to play with, just to show one of the cool features of Elm — since I'm watching the clock and I see we're close to time — is we can… Let me back up. Have you heard of the pipeline operator, Ben?

[00:48:01] Ben: Yes. So this is… My summary of it is basically you pass a value to a function and then you pass the return value of that into another function and so forth and you can keep chaining it, as opposed to, like, wrapping things in function calls in function calls in function calls. Is that… Are we talking about the same thing?

[00:48:23] Lindsay: Yeah, that's exactly it. So let's do something a little similar but in Elm. So Elm does have a pipeline operator.

[00:48:32] Ben: Okay.

[00:48:32] Lindsay: And one of the really cool use cases for it is when you have a list of things or you have an object or something and you want to pass it through a pipeline of changes.

[00:48:42] Ben: Okay.

[00:48:43] Lindsay: So we're going to see how that works and we're going to try… uh, words. So what we're going to do is take our list of people. We're going to sort them by the favorite number.

[00:48:56] Ben: Okay.

[00:48:58] Lindsay: And then we're going to display the person on the screen as HTML. So let's change our function just a little bit. Could you break it out to a new line

[00:49:08] Ben: Yeah. And actually, do you want me to comment this so we can hold onto it and maybe start anew?

[00:49:12] Lindsay: Yeah, yeah, let's do that.

[00:49:14] Ben: Yeah, let's do that. Okay, so main, and then I assume we're starting with our Html.div here, and passing…

[00:49:21] Lindsay: main =, but

[00:49:21] Ben: yes.

[00:49:22] main =, yes. Pass it empty attributes.

[00:49:28] Lindsay: Let's just go to the second line now, just to make this a little smaller. Four spaces. And an open paren. And then we're going to do people, which is our people array. And then under that… go to the next line. Sorry. The… words. The end paren is going to be at the very end of everything. Perfect.

[00:49:58] So go to the next line. Four more spaces to get indented. And then we're going to do the pipe and a right angle bracket. Just like that. So that's going to make… it's going to make a triangle shape, is the goal.

[00:50:15] Ben: Yeah, and this is, I believe, the exact same operator, like, down to the characters, that is coming to JavaScript, I believe—

[00:50:23] Lindsay: It is.

[00:50:23] Ben: —if you've followed the TC39 proposals.

[00:50:26] Lindsay: Yeah. The main difference we're going to see between the TC39 proposal and this one is that the special character you need to inject the returned value doesn't exist, so whatever our last argument is is going to be where the return value ends up as an argument to the next function.

[00:50:49] Ben: Interesting. Yeah, 'cause JavaScript has, like, this concept of, like, the question mark, which is like, you apply whatever the return value from the previous step of the chain was, and it's like a question mark, I think is what they're considering. Or maybe it's like a caret? Might be the caret now.

[00:51:05] Lindsay: Yeah, I've seen a couple different proposals.

[00:51:07] Ben: But it lets you basically say, like, you could choose where in the argument list you wanted to apply it.

[00:51:15] Lindsay: Right.

[00:51:16] Ben: Like that. But you're saying that Elm doesn't have anything like that. It's equivalent to always passing it in here at the very end, no matter what.

[00:51:26] Lindsay: Yes.

[00:51:27] Ben: Cool.

[00:51:28] Lindsay: Yeah. And this works really well for piping a value that is going to either be changing its shape as you go, or just something that you want the same shape and you want to apply a bunch of functions to.

[00:51:39] Ben: Yeah.

[00:51:39] Lindsay: So if you're familiar with the array functions in JavaScript — you might do a list.sort().reverse().map().… you know, something like that, and you're just calling it one after the other. It's the same idea as what we're doing here.

[00:51:54] Ben: Yeah.

[00:51:55] Lindsay: So in this case, we're first going to call List.sortBy.

[00:52:01] Ben: Camelcase?

[00:52:03] Lindsay: Just like that. You got it. And then we're going to have another lambda function. So parentheses, backslash, person. And all we're doing here is we're providing the key to the List.sortBy that we want to sort the list by.

[00:52:19] Ben: Okay.

[00:52:20] Lindsay: So let's do the arrow, and then let's just sort by number.

[00:52:23] Ben: So it's person.number.

[00:52:26] Lindsay: Yup. And next line. And do another triangle.

[00:52:34] Ben: Getting my spaces all right.

[00:52:37] Lindsay: Yeah.

[00:52:39] Ben: I… maybe I need to go in and unset this, but I was very insistent that VS Code, like, "no, you will always insert tabs," and it's crushing me now that, like, this is not a tab language.

[00:52:50] Lindsay: I think you can change that down at the bottom right with the tab size, right? If you click on that you can change it per file.

[00:52:59] Ben: Ohhh. Oh, okay.

[00:53:01] Lindsay: Yeah. Convert to spaces. And now it's going to be "Spaces: 4" for now.

[00:53:06] Ben: Okay.

[00:53:07] Lindsay: So let's just do List.reverse now. And that just takes in a list and reverses it, so there's no additional arguments there,

[00:53:15] Ben: right.

[00:53:15] Because it's already received… like, this is an array, this returns an array, and then that array gets passed here, so we don't need to say… Yeah, okay.

[00:53:26] Lindsay: Exactly. So we'll do one more here, and now we're going to do our where we return some HTML. So you can just copy it from the commented out one, too, 'cause it's the same.

[00:53:40] Ben: Okay. That was this up here? There we go.

[00:53:46] Lindsay: Two more symbols, but yes.

[00:53:50] Ben: Yes.

[00:53:50] Lindsay: Yep.

[00:53:50] Ben: Cool.

[00:53:53] Lindsay: Perfect. So now what we're doing is we're sorting by the number, we're reversing that, and then we're mapping over it—

[00:53:59] Ben: Okay!

[00:53:59] Lindsay: —and turning it into HTML. So if we go to our screen, we should see it in some order. Which in this case is no different, but if we remove the List.reverse

[00:54:07] Ben: Ahhh.

[00:54:08] Lindsay: …we'll be putting Ben first instead of Lindsay.

[00:54:12] Ben: Nice! Yeah, okay.

[00:54:14] Lindsay: Cool.

[00:54:16] Ben: By the way—

[00:54:16] Lindsay: I see that we are close to time.

[00:54:19] Ben: Yeah.

[00:54:19] Lindsay: So that's probably as far as we're going to get at the moment, but this, I hope, gave a taste of some of the syntax and some of…

[00:54:26] Ben: Yeah!

[00:54:26] Lindsay: …how Elm works to help you as a developer.

[00:54:30] Ben: Yeah!

[00:54:30] Lindsay: And then as you build out the application, it continues to help you as you go. So as things scale, Elm is able to keep in mind, "Oh, you have a value over here that's this type. It needs to be that type over here." As you make changes to your API like we were doing with greet, it will warn you these are all the places that you need to fix it. So it becomes a lot more straightforward to do a large refactor than if you were just working in something like TypeScript where it'll tell you in that specific file, but it might not tell you in all of the files and things might still compile depending on how you set your configuration, and especially in JavaScript where you don't get any of that benefit.

[00:55:10] Ben: Absolutely. Yeah, so like you said, this was just a taste of Elm, right? Where would you recommend folks go if they were interested in learning more about Elm and really picking this up to use it, like, in more fully-featured applications and such?

[00:55:30] Lindsay: So there are three different resources I would point you at. The first… Let me make sure I have the links up. The first is the Elm website, right there on the side under "A delightful language for reliable web apps," there is a guide, and that will walk you through the basics of Elm and how to do things. So as we were going here, we were kind of walking through the same basic concept, but so you'd be able to pick it up from the start and learn more about Elm as you go. You can learn about the Elm architecture, which is how full applications that take user input are handled. Learn more about types and error handling and how to do more complex things like HTTP requests. So this is a very good resource to start with.

[00:56:13] The second one I would mention is called Beginning Elm, which is at

[00:56:19] Ben: elmprogramming… That's no hyphens or anything like that?

[00:56:23] Lindsay: No, no hyphens.

[00:56:25] Ben: Okay.

[00:56:25] Lindsay: Just So this bills itself as "a gentle introduction to the Elm programming language." This is very similar in concept to the Elm guide, but goes a bit more in-depth.

[00:56:35] Ben: Okay!

[00:56:35] Lindsay: So they help you with building a simple web application and walk you through some of the key features with an actual example. So that is a great resource.

[00:56:45] If you want to take it, another resource that I would recommend — this is on — it is the book "Elm in Action" by Richard Feldman.

[00:56:55] Ben: Okay. "Elm in Action." I'm just gonna… "Richard Feldman." I'm just goinna google it and see what comes up. Here we go.

[00:57:05] Lindsay: There it is!

[00:57:05] Ben: Nice.

[00:57:08] Lindsay: Yeah. Richard also works at NoRedInk and this is an excellent book for getting started. Unlike the other ones, other guides, that are focused on getting across key concepts, this has you working on a single application from start to finish.

[00:57:24] Ben: Okay!

[00:57:24] Lindsay: And it hands you requirements in piece-by-piece steps so that you're able to start implementing them in Elm and learn as you go. So definitely recommend this book. I have a copy myself that I enjoy looking at.

[00:57:39] Ben: Yeah! I think Alex has just recommended again. Yeah. Okay, cool! So these… this is fantastic.

[00:57:48] And then, yeah, so you've been working on some tools for the Elm ecosystem as well. Like, we use today your Vite template. But you've got some other things you've been working on, right?

[00:58:02] Lindsay: Yeah! So the Vite template is first, and that was specifically because I needed a way to write Elm apps in Vite. I really like the Vite ecosystem and I wanted that integration as closely as possible. So that was the first one. The second thing that I would mention is called Elm Vue Bridge.

[00:58:20] Ben: Okay?

[00:58:21] Lindsay: And what that is… Yeah, you should be able to get to it that way. So Elm Vue Bridge is a tool… if you are somebody who writes in Vue and you want to try out Elm, it is a way for you to render Elm modules inside of your Vue application. So if you want to, for example, just try out Elm, some of the things that we were doing, and render it inside of Vue, this provides you a wrapper function so that you can take your Elm code, turn it into a Vue component, and inject it into your Vue template—

[00:58:57] Ben: Nice!

[00:58:57] Lindsay: —just like you normally would. It also provides some nice utility if you want to integrate a Vue and an Elm app together using the Vue API a little bit closer. So for example, you'd be able to pass in props and listen to events being emitted from the wrapped Elm module as if it was a normal Vue component.

[00:59:17] Ben: Very cool.

[00:59:18] Lindsay: So that would be my second suggestion if you're wanting to look at some of the things that I've been working on.

[00:59:23] Ben: Awesome!

[00:59:24] Well, Lindsay, thank you so much for your time. Thank you so much for showing us Elm. Y'all, go show Lindsay some love. Go follow her on Twitter. This has been great.

[00:59:36] Next week, we're going to have Alex Riviere on. You might have seen him around the internet as Fimion. We are going to be making some terrible web components and I mean terrible. His whole thing is building stuff that hearkens back to the GeoCities aesthetic, and so it is going to be absolute nonsense. If you like nonsense, you'll want to be there next week, 2pm Centra next Tuesday.

[01:00:01] And y'all, stick around. We're going to go raid… sounds like Aydrian's on, so we're going to go raid him! And y'all, thank you so much for being here! Bye, y'all!

[01:00:27] Lindsay: See ya!