Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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



Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: