14 comments

[ 3.4 ms ] story [ 42.2 ms ] thread
Sam's done a few of these now, and the level of detail is just getting better with each one.
yeah, i really like the achievement system for the interactive demos. it's a fun way to make sure readers are actually engaging with the lesson, and understanding its points.
Yes, very fun! Did you spot the easter egg at the end?
just went back and checked! (started running into perf problems by the last exercise)

very cool :)

Sorry about the perf problems! This is definitely my heaviest post. What device did you read on?
looks like it's a firefox (mac, v127) thing. i just tested in chrome and didn't get any issues.
(comment deleted)
I'm the author of this post, happy to answer any questions :)
hey sam! were there any other queue types that you decided to omit? and what were the benefits of web components in this article?
Oh loads, queueing has been around forever and there's an enormous amount of material on the topic. This post barely scratches the surface. One specific omission was an AQM strategy called "CoDel", which I'm expecting people to pick me up on.

Web components are just one method of componentising the visualisations. I'm steering clear of React/Vue/whatever other framework because I want these posts to still be relevant in 10 years. I'm not confident any existing frontend framework will be around 10 years from now, so decided to stick to web standards.