Javascript to Elm

We're getting into the good parts of building with Elixir. From data transformation to connecting to outside systems

This project is really picking up some steam. We need to shore up just a few things on our pipeline to make deployment easier. Migrations. Then we can start to really get into the domain of how we make this app to behave.

Gotta admit, once I got the auth working and the deployment going, I was a bit hesitant to start adding to the project again. Because that meant, failed builds, unknown errors, and a general sense of failing. We just got things working! But's the sayin' "if it's not broken, you're not working hard enough"? So back at it I guess.

Why start with auth? Mostly because anything we'd want to connect or do with our site will require some level of user input, credentials to accomplish. Could we start with something else, like a feature? Sure, but sooner or later we'll need user auth / profile. So head down let's get to it.

Remember what started us down the path of managing a kubernetes cluster in the first place? No, it wasn’t our own sadistic desire to to devops in an effort to avoid building an actual project, but close. We want to be able to leverage ‘live view’ in our project, that requires websockets, which all signs pointed to not available on appengine.

When we last checked in our our struggling hero, me, I was struggling with the Jungle that is AWS and it's layers and layers of AIM roles, services accounts, interwoven services, and endless dependencies. Step one. Oh snap. After a long hard slog, and what felt like death by a thousand tiny cuts, it's working. I now have a deployed Elixir Phoenix App, building, running, rolling updating, all by git commits.

We're doing it again. Avoiding actual work by playing around with Elixir using the Phoenix framework and I love it. Now, can we get it deployed in a reasonable way so that projects we work on can be shown off to the world?

I was gonna steer clear of this topic after initially reading the post by Chris Gregori Elm and why its not quite ready yet , and the follow up by Lucas Payr How Can the Elm Community Improve , but it sort of festered on my mind, which listening to this reason behind this weeks tardy release. I have another episode in the cooker, one that was a lot more fun to work on, but there was something about this open conversation that I just can't shake.

Covering the current state of open source support both monetarily and emotionally to those that put in so much work and effort that everyone benefits from.

The year is half over! Now's a good time to take stock of our yearly themes and see how we've done sticking to it and what we can to to improve parts, and to also celebrate what we've been doing well.

Coming down from our conference high, we've also thawed out from the 'Spring' temperatures in Chicago, we get back to work on routing and overall structure on building a SPA in just Elm.

A rundown of our whirlwind trip to Chicago for what will hopefully be the first of many Elm in the Spring conferences. The talks where great, the community is awesome, and we explore the tinge of jealousy for those working in Elm on a day to day basis.

Further down the rabbit hole we go with routes from pages to components. We avoid actually getting to the topic at hand pretty well, but eventually tackle it, get lost several times along the way. Come along and get totally turned around with us!

We revisit an old friend from episode 51 - Elm Routing (Maybe) about routing in Elm. Let's see if we've learned anything in the last 20 something episodes?

We get a chance to talk with Blake Thomas co-organizer of Elm in the Spring, coming up in just a couple weeks in Chicago. We cover bringing Elm into an organization, coding confidently, sustainability, and a variety of random topics.

We have a chance to catch up with Gatsby Developer

We run through our actual talk with slides you can't see bc #podcast, but you get the idea. Getting out all the nerves before our first conference talk, now just days way!

We've got nerves about our big conference talk next week. Trying to finish up the slide deck and practice on anyone who will listen, and resist the temptation to keep changing the deck.

So are we learning or are we wanting to build something? Can it be both? Do we even have the right expectations and goals set? Let's talk it out.

Just realized that looking at language extensions sent me down a rabbit hole on Macros, and I might have gotten myself totally turned around.

After we've spent a comical amount of time getting a Linux environment setup it's time to actually try to get Haskell running on aws lambda.

We started with an idea to use Haskell on AWS Lambda so we didn't have to deal with OS setup, config, update, and headache. By the end we found ourshelves partitioning our local drive to dual boot it into Linux, running `sudo apt update` a dozen or so times. How did things go so wrong?

It's the year of the blog. And Linux on the desktop. lol. We talk about some of the more simple pleasures of building a website for personal blogging, getting into the CSS and actual HTML tags, not just generated webpack bundles. And yeah, at certain times we get old timey for RSS readers and irc.

We are trucking right along on our Haskell mini-series, doing every exercise on every page. When we aren't knocking that out, we are trying to get 20 conference rejections for the year of 2019. So let's check in and see how it's coming along.

We are getting to apply all that theory we went over into command line examples, building on what we've learned brick by brick. It's getting pretty exciting to actually understand most of what's going on!

We have made it to the beginning! With a solid understanding, or at least a better understanding we are ready to tackle I/O, aka side effects!

We layout our themes for the upcoming year, not to be confused with resolutions or goals, these are a bit different than you might be used to.

We've tackled Semigroups, and with a little more effort we can better understand Monoids too. With all this momentum we'll cover parameterized types and the Maybe type too.

Sticking with Types, we dive deeper with sum and product types, we hit on Semigroup and start to unwind Monoids!

Things are starting to click into place slowly. I am feeling more confident in reading and thinking type signatures and composability functions. Best of all, I am really enjoying it.

We're moving pass primitives and diving into types, types, types. I've really struggle with this in previous Haskell attempts, this is usually the part where I get frustrated and bail, but not this time!!!

We are cruising right along. Getting some of the finer details of list, recursion, closure, and pattern matching in Haskell down!

So here's the deal. How many times have you tried to learn Haskell? We're gonna give it another run at it.

We go from planned topic to full scale book review. But we've strung together a small string of victories, and that feels pretty good.

You thought maybe this week would be about Rust didn't you! My thought was I **MUST** finish meow notes into ALL Elm before I even think about diving into Rust to replace the backend. And that leads us into staying focused.

Types, types, types we are really trying to get our head around parametric types, and then take that the extra step to dependent types. Keeping in mind, that a type, is just a set of values, not some over whelming academic secret conspiracy to keep you in the dark. (that last part was directed at myself) Then we end up having an epiphany!!

We start with my addiction to programming books, and end with dependent types, that's a logical path, right?

Huge thank you to all the people that worked to make Elm Conf possible. I had a fantastic time. Let's find out if I made my goal to remove react from our project entirely and my experiance at Elm Conf.

We are coming down to the wire to get the rest of our app from React to Elm. Router has been a huge hang up for us this last week. Might be through the tough parts. Let's find out.

We are trying our best to make the self imposed deadline to have our app converted by Elm-conf. Let's dive in and see what went well, where we struggled, and what we did to procrastinate.

We avoid starting and do a bunch of other things to make us feel productive, like cleaning out our bash_profile, or making new Dockerfiles. Eventually we buckle down and get started on the last part of pulling React out of our project.

We are currently avoiding meownotes for no real good reason, other than we're not really sure where to start. So, since we are super successful at that, we expolore all the other things we've done, besides what we should be doing!!

The red square. If you recall from episode 46, we were trying to get a web component (a div in the shape of a square, with a red background) to render in our application. Well, we figured that out and a whole lot more.

It's here, it's here. We all woke up in the morning to a fantastic gift, we're talking all things Elm 0.19 was released today. Let's dive in and take a look!

We want to dive in and actual tackle a web component. And what better way than with meownotes. We are going to try and upgrade the text input from textArea to super duper markdown editor using JS Lib custom web component.

There was a presentation locally on ReasonML, so I went and learned. We'll compare it to our experience in React our current favor Elm, and what we can take away from this new player in the frontend space.

Based on 2 events. Luke Westby's talk at Elm Conf, and the most recent episode of the frontend Happy Hour podcast about.... web components. So I've heard about them, and meh, didn't seem to solve any immediate problems I've been having, but I don't actually know enough about them to actually apply them to any problem I encounter!

Do it already?!?!? What's the hold up? Where are we with new notes page in Elm ? I needed to make a list. So here it is, let's go through it.

We've done some great refactor work, but forgot one of the rules to our project. Keep it working, keep it in production. And our elm branch for new Notes is neither in production, or even fully functionaly in our dev environment. We always fine some small gotcha's when we have to double back, let's get to them!

So we have been avoiding wrapping up our new Note page converting it over to Elm, and in that respect we've been doing a pretty good job I'd say. I feel like it was a huge first lift to get most of it working, which is why I've been hesitant to dive back it, I know, at least for me at this point, it's going to be a bit bumpy, but what the hell, makes for good podcasting.

From local webapp Rocket with Rust last week, to getting the whole thing into production. If there's one thing I've learned over the last year, it's that any evaluation/project/proto-type/mockup/thing is best examined by taking it from localhost all the way to **PROD** before making any rash decisions. I'm not going to lie, this was really difficult to accomplish.