Check out my new course Learn you some Lambda best practice for great good! and learn the best practices for performance, cost, security, resilience, observability and scalability.
- Pythagoras Tree
- Cantor Dust
- Koch Curve (this)
- Sierpinski Triangle
- Dragon Curve
- Fractal Plant
Example 4 : Koch Curve
Once again, we will start by defining our L-System:
From here, there are a lot of similarities with our implementation for Part 2, so time for a minor refactor!
We’ll add a shared Path module, and move the common abstractions and helper functions there:
Over the course of the series, we’ll add to this common module to help handle other aspects of drawing our L-Systems.
For the Koch Curve, the only thing we really need to implement is the display function to handle ‘F’, ‘–’ and ‘+’:
“Here, F means “draw forward”, + means “turn left 90 degrees”, and – means “turn right 90 degrees”..”
So this was what I ended up with as a 1st pass:
OK, so that was a lot of code to digest, so let’s break it down a bit.
The most important bit of code is here:
where we implemented the logic for:
- ‘F’ : draw a line segment
- ‘–‘ : turn left 90 degrees
- ‘+’ : turn right 90 degrees
in a left fold over the current state, using the starting position (0, 0) and rotation angle 0 (radians).
But, what’s this canvasArea that’s passed along?
Aha, good, you caught me! I’ve secretly added a little something to the Path module:
These are to help me track the area that has been drawn on so that I can use this information to scale down and move the completed path later on so that it fits inside the collage and is centred.
Whenever a new segment has been added the ending position is used to expand the canvas area:
At the end, we work out the scale factor, and move the path to the centre of the collage:
As it turns out, much of what’s in the display function is the same across most of the examples, so let’s refactor and move it into the Path module:
and our Koch Curve implementation becomes much simpler:
Running this example in Elm Reactor I can get the demo to gen 6, before the rendering time starts to go up noticeably.
Live Demo (here)
Use LEFT and RIGHT arrow keys to evolve/devolve the L-System.
Source Code (here)
Next : Sierpinski Triangle
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, Learn you some Lambda best practice for great good! In this course, you will learn best practices for working with AWS Lambda in terms of performance, cost, security, scalability, resilience and observability. Enrol now and enjoy a special preorder price of £9.99 (~$13).
Are you working with Serverless and looking for expert training to level-up your skills? Or are you looking for a solid foundation to start from? Look no further, register for my Production-Ready Serverless workshop to learn how to build production-grade Serverless applications!
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