This is correct, they were independent works. It’s spoken about in “The Annotated Turing” by Charles Petzold.

I love it. I love it so much.

When I was working on this post I found the way that Turing defined “computable numbers” I bit unsatisfying as well.

What would you suggest I do to deliver on this?

I would suggest to not promise it. ;)

Maybe rather:

• That some truths cannot be computed.

I’m not sure I understand. I do explain what can be computed, don’t I?

> Something is said to be "computable" if there exists an algorithm that can get from the given input to the expected output. For example, adding together 2 integers is computable.

I could probably have dug into some of the restrictions, like how it has to be a finite number of steps.

This defines the term “computable”, but it doesn’t give you a sense of what things can be computed. Defining a term is entirely different from the above promise.

At the level you’re describing Turing machines, it’s also not clear that readers would have a precise notion of what an algorithm is. At no point (unless I missed it) do you explain that any algorithm is supposed to be implementable as a Turing machine, or the assumption of what is otherwise known as the Church–Turing thesis.

That’s true, there’s no explicit definition of what an algorithm is. I may revisit this. Thank you for the feedback.

I watched a fun talk in preparation for this post on unlimited register machines that you might enjoy: https://youtu.be/7Q-UwjgZ0q4?si=abEV1JKd9kuI8w8z

Thank you <3

I’m the author of this post! <3

Happy to answer any questions you might have, and love to hear feedback good and bad.

Can confirm. Received the first email here from Justin and it worked on me.

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.

I'm the author of this post, happy to answer any questions :)

Hi Sam, what are you using to make the animations?

PixiJS and GSAP :)

You can see my code here: https://github.com/samwho/visualisations

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.

Thank you <3