There’s a new-look online debugger which looks prettier than before:
but more important than that, is the new Elm Reactor command line tool which powers both the online debugger. With the Elm Reactor you can run your own time-travelling debugger locally and as you edit your Elm source files you can watch your application update in real-time while retaining the ability to go back in time by play back previous events.
There’s also a new command line package manager – Elm Get – which gives you the ability to easily add community Elm libraries to your project, or to publish your own libraries to the Elm Public Library. Overall it works very similar to the how Dart-pub works and whilst I haven’t published any libraries myself it seems a straight forward affair.
There are a couple of small breaking changes in the core language, and it’s great to see that F#’s functional composition operators (<< and >>) have been adopted and released in this version!
Now that I’ve caught up on the changes, I put together a simple implementation of Snake, and to my pleasant surprise the whole thing came in at less than 100 LOC although admittedly not the easiest 100 LOC I’ve ever written. I had to really think about what I’m doing (which is a good thing), the lack of IDE support occasionally gets in the way, and I find the error message hard to read sometimes (although it’s much better formatted when you work against Elm Reactor running locally.
If you’ve got a few minutes to kill, why not give it a go:
and feel free to check out the source code on Github.
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong