Javascript to Elm

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.

I have, for a long time, wanted to stretch my functional type safe ways into other areas of programing, to better round out my skills. And I waffled between backend languages quite a bit. If you follow us on twitter, you likely remember questions about which language would you dive into? More Haskell ? Maybe something with JVM like Scala, or Elixir with the Phoenix framework? Possibly Rust?

Hope last weeks talk was enjoyable. Back to our refactor of meownotes. Tackling some of the more _interesting_ parts of the new notes page. Things that I've been avoiding, like file upload, mostly because I knew I'd need to modify my model, Interop some things, **AND** deal with type Maybe.

A special live recording of my talk at Elm Eug on Elm View, the showdown. A continuation of the first and second blog 'Blazing Fast HTML' Parts 1 and 2, comparing Elm render time and optimizations against other frameworks out there.

We find that looking closer at replacing new note creation isn't as easy and 1, 2, 3! Who would have that. You'd think after the 10,000th time we'd learn, it's never as straight forward as we thought. Ok, so let's regroup, come up with a strategy for getting this done and go from there.

We've made a lot of progress over the past weeks and months. It's time to sink our teeth into New Notes form. At it's basic we want to have the text into, attach a file, and a create button. And then more!!!

So we are at that point when it's time to expand our app to have more than a single component in Elm. A couple weeks ago we started down the path of routing, by refactoring the core of our app, main state and routing, into Elm. This turned out to be a bit more daunting the more we looked into it. So let's try something else...

So I all the rewriting and refactoring, we haven't shipped out a release of meow notes in a while. The first rule of our refactor was to always keep it in a state of usability. That way problems we have, or choices we make will come up sooner, rather than later!

As I'm looking at the ways that I can get tackle having Elm over take our React app, I'm a bit stumped by routing. For review, we've got an onClick event in our list of notes in the 'Home' module that should take use from the root of our application '/', to notes with at unique noteId in the url like '/notes/:noteId'

My thesis is that in a few short years JavaScript will be considered in the same realm as programming in C. Meaning to write an application in JavaScript will be considered “mid level”, error prone, dangerous (dangling pointers), lowest common denominator, and only really used when you need to leverage a specific use case.