The undersea cables actually connecting the entire internet. Sometimes sharks just take a bite of them, they're reasonable well protected but it's enough damage to cause outages and disruptions.
It's the single pin under everything because there are a limited number of those cables especially in some regions so a single shark can take out the entire internet for some countries.
I feel like having them as a single brick is a bit hyperbolic, since undersea cables are pretty redundant in most of the world. Get rid of one and traffic just routes around it. Ships have been routinely destroying cables in the Gulf of Finland and the Baltic Sea in the past couple of years without causing significant disruptions.
Register the mousemove event handler on window, then you will still get the events when the mouse moves out of the window/frame while dragging and it won't be that buggy.
On my machine, the initial state isn't simulated. It only begins simulation when I touch it. At which point, the weight causes the bottom blocks to intersect each other significantly.
If I open it, click on the background to activate the physics and just keep the tab open, pretty much all of the blocks that can collapse do eventually collapse.
One more pedantic nitpick: when a block gets wedged between two blocks at an angle, it gets slowly pushed out, although there is a lot of weight resting on the top block. That would be realistic only (maybe) if the blocks were made of ice, but not for other materials...
But then, when trapped in a local maxima prohibiting growth, pressure builds as too many new layers attempt to shim themselves under existing layers, until inevitably the stack collapses somewhere.
Then new layers can restart generating new apex baby layers on a now higher foundation of fertile fragmented but compressed and stable new-legacy rubble. Another point-oh age begins.
And sometimes, the stack just falls apart because.
In between those extinction events, layers that spawn the most layers, and form opportunistic bridges over lateral layers, dominate and thrive.
Occasionally, some layers try to reorder themselves to optimize future growth. Or tunnel down to achieve stronger footing. But like the tower of Hanoi, the more layers involved, the more intractable the replanting and reordering. Meanwhile, other growth routes around them. Yet, many instances of these failed structures can be found in the depths.
Did you actually manage to remove a block without everything collapsing (eventually)? Then you must have an incredibly steady hand, it's nearly impossible to do as far as I can see. Which can also be interpreted as a metaphor for the state of the tech stack, I guess...
Very satisfying. I ripped out the load bearing piece and everything stayed standing except for the tiny pieces at the very top. Doesn't seem so bad according to the simulations, maybe we could use a good shakeup?
Really cool! To be honest, when I clicked on this I had a hope that it would be possible to add things to the stack like the ongoing memes of just putting different things in there (maybe live with other people as a collaborative editor).
It's 2,347. There's also 927. And 538, and who can forget 386. 936 is also a classic. 1205 is a favorite, although AI changes the scales these days. As does 303. 1838 is another good one for when CC is "thinking". 1425.
It'd be really cool (and probably useful) if someone could figure out a way to generate diagrams like this for any software project.
You'd first need to figure out a way to generate a complete dependency tree. For each box, I interpret its height as a measure of its complexity and its width as a measure of the support it receives. The hardest part would probably be figuring out a way to quantitatively measure those values.
I don't know if the "The Nebraska Guy Ranking" this project uses is very useful, though. In particular the "depth" criteria doesn't make much sense to me, since it assumes the more foundational a dependency is, the more robust it must be. This seems to run counter to the point of the original comic where the "Nebraska Guy" piece was the fragile block holding up the entire tower.
This project also doesn't attempt to measure or visualize the complexity of a project. Theoretically a more complex project would require more support than a simple one, so I think that's an important metric to capture.
> If only it wouldn't collapse by itself after clicking anywhere (clicking seems to activate physics) this would be 10/10
I think that's the other metaphor here.
It's not just standing on the tiny shoulders of one forgotten maintainer. The entire system only appears stable because we're looking at a snapshot of it.
Not sure. It's not it being unstable, it's small bricks moving bigger stuff to the side and maybe even upward. If I missed the joke I just don't find it funny.
Is this website intended to break HN on Android? I've never had a website lock up the HN app like this. I couldn't back out, and I was stuck in a loop when the app restarted on the same page.
The AI crank always cracks me up.
It's the single pin under everything because there are a limited number of those cables especially in some regions so a single shark can take out the entire internet for some countries.
http://www.mirceakademy.com/uploads/MSA2024-6-6.pdf
Thank you for the laughs. I needed that!
The world keeps moving around us. Can't choose staying still.
But then, when trapped in a local maxima prohibiting growth, pressure builds as too many new layers attempt to shim themselves under existing layers, until inevitably the stack collapses somewhere.
Then new layers can restart generating new apex baby layers on a now higher foundation of fertile fragmented but compressed and stable new-legacy rubble. Another point-oh age begins.
And sometimes, the stack just falls apart because.
In between those extinction events, layers that spawn the most layers, and form opportunistic bridges over lateral layers, dominate and thrive.
Occasionally, some layers try to reorder themselves to optimize future growth. Or tunnel down to achieve stronger footing. But like the tower of Hanoi, the more layers involved, the more intractable the replanting and reordering. Meanwhile, other growth routes around them. Yet, many instances of these failed structures can be found in the depths.
Of course, glad to see it was another @isohedral project.
Previously I'd postpone some tooling since I'd lost more time on it (unless it's something I wanted to learn anyway), but now I'm all in.
"The Internet Was Weeks Away From Disaster and No One Knew"
https://www.youtube.com/watch?v=aoag03mSuXQ
(at about the 9:50 mark)
I know the time it takes to get something to feel this good.
Really fantastic work.
Edit oh and Extrapolating out; 605.
https://bash-org-archive.com/?5273
Half the fun of this xkcd is referring to it in context of whatever just went haywire.
That text is literally the only thing hardcoded. It's inside a PNG, sourced in.
I get it though. Reproducing that cutesy "hand drawn" text would be a pain in the arse if you didn't just have the font.[1]
You'd first need to figure out a way to generate a complete dependency tree. For each box, I interpret its height as a measure of its complexity and its width as a measure of the support it receives. The hardest part would probably be figuring out a way to quantitatively measure those values.
I don't know if the "The Nebraska Guy Ranking" this project uses is very useful, though. In particular the "depth" criteria doesn't make much sense to me, since it assumes the more foundational a dependency is, the more robust it must be. This seems to run counter to the point of the original comic where the "Nebraska Guy" piece was the fragile block holding up the entire tower.
This project also doesn't attempt to measure or visualize the complexity of a project. Theoretically a more complex project would require more support than a simple one, so I think that's an important metric to capture.
I think that's the other metaphor here.
It's not just standing on the tiny shoulders of one forgotten maintainer. The entire system only appears stable because we're looking at a snapshot of it.
In reality it's already collapsing.