Hacker News new | ask | show | jobs
by dogma1138 539 days ago
Backward compatibility is one thing but not having a forward compatibility is a killer.

Having to create a binary that targets a very specific set of hardware and having no guarantees and in fact having a guarantee that it won’t on future hardware is what make ROCM unusable for anything you intend to ship.

What’s worse is that they also drop support for their GPUs faster than Leo drops support for his girlfriends once they reach 25…

So not only that you have to recompile there is no guarantee that your code would work with future versions of ROCM or that future versions of ROCM could still produce binaries which are compatible with your older hardware.

Like how is this not the first design goal to address when you are building a CUDA competitor I don’t fucking know.

1 comments

> Like how is this not the first design goal to address when you are building a CUDA competitor I don’t fucking know.

The words "tech debt" do not have any meaning at AMD. No one understands why this is a problem.