A collection of posts about my favourite topics in programming
I have been working on a personal project of mine for the last couple of months that has the frontend written in Elm. So far everything is going great and the project is around 10k lines of code.
I have noticed a few reoccurring patterns of mine that I have learned so far and want to share, so here are 5 things I have learned:
- Decoding Empty Lists & Strings When I first started the project, I had a lot of types with fields declared like this:
Pratica is now written completely in Typescript!
What is Pratica? Pratica is a super tiny 720B monadic library, comparable to Crocks or Monet JS.
Often in web development there is this recurring pattern of having to fetch some data from some server through a rest api, and then show it someway in the UI.
This often includes storing this data somewhere on the client side, either in a store or just a variable you can reference, and this is where the Remote Data type can help.
Usually saving the data would look something like this in JS:
I have recently been exploring creating web apps in Elm and found it to be a breath of fresh air compared to the usual React/Redux projects I have worked on in the past.
*Disclaimer: I still think React/Redux is great and viable for large teams if done correctly. This article will just explain my pain points with it while working on large teams at various companies, and why I think Elm can be a better alternative in some cases.
I recently gave an internal talk at my work about the similarities of F# compared to JS. It was generally well received, and I would like to convert that talk into a blog post for others who may be interested.
This is by no means an exhaustive list of features in F#, but the point of this post is to show familiar JS code and how it can be written equivalently in F#, because I believe showing examples like this is the best way of learning a new language and has a better chance of adoption.