4 ms·
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
by nneonneo 1y ago
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://www.youtube.com/shorts/ue2gZ2vxs48
https://engineering.purdue.edu/ECE/News/2025/purdue-ece-students-shatter-guinness-world-record-for-fastest-puzzle-cube-solving-robot https://engineering.purdue.edu/ECE/News/2025/purdue-ece-stud...
- hammock 1y agoRobotic 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
- teiferer 1y agoFirst, 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?
- rossant 1y agoMaybe there's a new instruction we don't know about in modern CPUs, like RUBIK_SOLVE or something.
- SwiftyBug 1y agoI mean, we've had RUN_DOOM for many years now, so why not?
- amypetrik8 1y agoyes, in python either 1) "import doom" or 2) "from rubik import cube"
- Tempest1981 1y agoThey probably meant millisecond
- adrianN 1y agoI wonder how many cubes they exploded in the making of that robot
- hermitcrab 1y agoImpressive and a bit mad.