I tried this five years ago back when I was an engineer on the PyTorch project, and it didn't work well enough to be worth it. Has it improved since then?
It works, but there are fair amount of caveats, especially for someone working on things like Pytorch, the runtime is close but not the same, and its support of certain architectures etc can create annoying bugs.
I tried this recently and it seems like you have to make a lot of decisions to support Act. It in no way "just works", but instead requires writing actions knowing that they'll run on Act.
I tried act, on the surface it seems like a godsend. Not until you try to use it do you realize it's almost impossible to recreate any moderately complex workflow.
You HAVE to run it against a container, so if you're using self hosted runners your environment may not match at all.
I think most people wouldn't call Go a systems language? Generally garbage collection lack of explicit memory access would put a language outside the category? Hard to write a device driver, for instance.
True although there is Ocaml which has been used in OS/driver/Hypervisor development while also having a GC.
I always thought the Go equivalents would have perfomance at parity - but never reallyseen that realised so far.
Lets you run your actions locally. I've had significant success with it for fast local feedback.
reply