this post was submitted on 30 Nov 2023
2559 points (99.6% liked)

Programmer Humor

19623 readers
2 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Pazuzu@midwest.social 230 points 1 year ago* (last edited 1 year ago) (16 children)

I thought this had to be hyperbole, so I did the math myself. I'm assuming human history is 200,000 years as google says, and we want to narrow this down to the second the bike disappeared. also that the bike instantly vanished so there's no partially existing bike.

each operation divides the time left in half, so to get from 200k years (6.311×10^12 seconds) to 1 would take ~42.58 divisions, call it 43. even if we take a minute on average to seek and decide whether the bike is there or not it would still be less than an hour of manual sorting

hell, at 60fps it would only take another 6 divisions to narrow it down to a single frame, still under an hour

edit: to use the entire hour we'd need a couple more universes worth of video time to sort through, 36.5 billion years worth to be exact. or a measly 609 million years if we need to find that single frame at 60fps

[–] Syldon 4 points 1 year ago (3 children)

A minute to decide if there is a bike in the picture really ?

[–] Deuces@lemmy.world 12 points 1 year ago

As a robot, finding bikes in pictures is really hard, okay

[–] Pazuzu@midwest.social 8 points 1 year ago

Takes time to precisely seek to each timestamp, but really I just meant that an hour was reasonable even with a lazy cop doing the search

[–] sukhmel@programming.dev 2 points 1 year ago

They must be really bad at solving CAPTCHA

load more comments (12 replies)