There’s a hidden hole in the middle of the rollercoaster, and on the opposite side in the middle of the St Louis Arch. Bounce along the surface and you’ll fall into it eventually.
Yeah I got just past the arch, but I came to a little rectangular platform that I had a very difficult time getting over, and when I finally did there’s a much larger tower right next to it, which is where I gave up.
Yeah, I stumbled on that solution
Someone with way too much time created a map of the system showing the objects and powerups.
And, unsurprisingly, this is another one that does absolutely nothing except hard-crash my browser (Firefox on OSX).
You’d think that someone like Munroe would test these things out on multiple platforms.
There’s (basically) nothing you can do in Javascript that will crash your browser, unless the browser itself is broken or you have a system problem. Are you using some ancient version of FF? It works fine for me.
I know that. But still, I’ve got better things to do with my time.
I don’t think it’s possible to use “an ancient version of FF”. Every week or two it tells me it’s updated to the newest version. And clearly there’s something you can do in Javascript to crash it, but don’t ask me what.
The computer itself is getting pretty long in the tooth, and there are certainly some tasks that slow it down considerably, but I think the last time my browser actually crashed was the last time XKCD did one of these Javascript things. Well, that, and sometimes I intentionally quit Firefox and the crash-detector mistakenly thinks it crashed.
It’s definitely possible if your OS is out of date. People still running XP, for example, will be stuck with an old version. Dunno about MacOS.
Might be an out-of-memory situation. My browser tells me that tab is taking up 1.2 GB.
As someone who has written very complex programs in javascript… I really doubt it’s that bulletproof.
The browsers certainly aren’t bulletproof. But that’s on them, not the writer of the JS code. If you can crash the browser (aside from causing an out-of-memory condition), then you can cause a security breach. And that’s a serious bug on the part of the browser.
It just doesn’t work on mine: Firefox OSX 10.13.4 running NoScript, with every visible javascript (which isn’t much) enabled. I can see what looks like a still but it won’t do anything or go anywhere but home. Probably the browser’s blocking some bit of script but not showing it to me so I can enable it.
And it doesn’t work on my iPad, on which it loads OK but I can’t control anything, because apparently you’re supposed to use your keyboard arrows and the popup onscreen keyboard a) doesn’t have any and b) covers the display. Tapping on the screen produces a certain amount of bouncing, but no control. I suppose I could hook up the bluetooth keyboard to the iPad, but it doesn’t really seem worth it; I can waste more than enough time doing something else. (This, for instance.)
This is a pretty accurate description of how it works properly on my phone. (Pixel 4a.) Tapping produces a certain amount of bouncing, and it took me an embarrassingly long time to figure out how to make those taps control the direction. (Tapping on the sides of the screen instead of just in one place.)
And then I was almost to the furthest point I reached before I realized you could do a long tap to hold the thruster on. And then I gave up.
Remember Little Bobby Tables? I saw a picture that reminds me of him.
One of my fonder memories from high school was figuring out that that mysterious “ln” button was some sort of logarithm, and asking my math teacher just what the significance of this “2.718…” number was.
Although, I didn’t twig to the fact that the inverse of the function was on the same button, and had to figure out the value of e through the method of bisection.
Until I got to the alt-text I thought the shape he was referring to was the lenticular intersection part.