Related - there's a Guinness record for the fastest Rubik's cube solving robot; it stands at 103 milliseconds:
https://www.youtube.com/shorts/ue2gZ2vxs48
https://engineering.purdue.edu/ECE/News/2025/purdue-ece-stud...
Related - there's a Guinness record for the fastest Rubik's cube solving robot; it stands at 103 milliseconds:
https://www.youtube.com/shorts/ue2gZ2vxs48
https://engineering.purdue.edu/ECE/News/2025/purdue-ece-stud...
I wonder how many cubes they exploded in the making of that robot
Impressive and a bit mad.
Robotic solver is more of a physical problem than a mental one. A photo of the cube from top and bottom corners and you can solve it in a nanosecond
First, you still need to optimize the solution to fit the constraints of mechanical solving. It needs to be as few moves as possible, some of them are parallelizable, etc. Not a trivial problem.
Second, nanosecond? You know that a GHz CPU does a single clock tick in one nanosecond, right?
Maybe there's a new instruction we don't know about in modern CPUs, like RUBIK_SOLVE or something.
I mean, we've had RUN_DOOM for many years now, so why not?
yes, in python either 1) "import doom" or 2) "from rubik import cube"
They probably meant millisecond