52 comments

[ 1.4 ms ] story [ 74.7 ms ] thread
I wonder how much email this person is receiving from the mailto at the end
I'd say he missed out on an opportunity to use that button to build a viral feedback loop! I honestly thought it was an "email to friends" button.
Professor Plum choked on a prune, and coughed up an idea for making the web worse.
Err... how do you start it?

EDIT: Just a network hiccup apparently.

EDIT2: Though I really wish it played Danny Elfman's "Breakfast Machine" like the old days of the ball machine animation...

Do you have Javascript enabled?
I don't understand how this is a Rube Goldberg machine. Everything that happens is triggered by a Javascript setTimeout call, not from the action that happened before.
It's meant to look like one, even if it technically isn't implemented as one.
A Rube Goldberg machine is a contraption, invention, device or apparatus that is deliberately over-engineered to perform a simple task in a complicated fashion, generally including a chain reaction [from wikipedia]. In this example, the simple task is displaying the email button. And most computing operations are Rube Goldberg state machines if you think about it, no?
I think the point was that it's not really a chain reaction as each action has its own timer and will happen regardless of if any other action completes or doesn't complete.

Which is not to say I didn't thoroughly enjoy it :)

It's an asynchronous embarrassingly parallel Rube Goldberg machine ;)
I wonder if it was intentionally implemented this way, would memory have been an issue with the amount of callback chaining required?
> would memory have been an issue with the amount of callback chaining required?

Unlikely; you gotta hit a really deep stack to really kill something with callback chaining.

It could have used a start button that sets focus to the first one and then each focus change makes it go to the next but without the setTimeouts it would go by so far it wouldn't be nearly as fun.

(comment deleted)
You could still add a delay function with a setTimeout, but you'd only need one.
Would be cool if it used a huge callback or promises chain. Still cool/fun concept.
This is genius. So simple yet so amazing. Reminds me of the Blue Ball Machine
Neat though its code could have been significantly simplified through the usage of some focus events and using tabindex to iterate over each field (to a degree; some items would require a little bit more fancy-ness but not much).

Also this page has the biggest html table I've seen in years :)

People are already complaining that the code isn't Rube Goldberg enough as it is, and you want to simplify it even further?! :)
This is really cool,though I really wish I didn't look at the source code.
CSS and Javascript mixed with HTML, that's a pain to look at.
Yeah, I guess. This is art, not software, IMO.
Fantastic, I really enjoyed it.
Recently had to rube goldberg my HTML form POST's to work with API Gateway because of this issue: https://forums.aws.amazon.com/thread.jspa?threadID=205782. Work around I came up with was a ridiculous redirect chain utilizing JWT. This is much prettier though.

If anyone is interested, it seems like you can probably get away with ~20 temporary redirects before your browser starts complaining about redirect loops.

Considering this was written by a Dane (assuming from the TLD alone), the author might personally have referred to this as a »Storm P.-maskine«.[0] I know I would (being a Dane and all).

[0] https://en.wikipedia.org/wiki/Robert_Storm_Petersen

I'm pretty sure most frontend work with Javascript is already a Rube Goldberg machine.
The use of setTimeout makes this an animation, not a chain of events.