3 ms·

Yeah, I've ranted about this here in the past. I'm glad someone high-profile enough is finally doing the same, as that might actually lead somewhere. Their clo

Yeah, I've ranted about this here in the past. I'm glad someone high-profile enough is finally doing the same, as that might actually lead somewhere. Their closed development process is so moronic. It means their code is always ahead and out of sync with what is in public. There have been user provided fixes and improvements to ROCm on GitHub with no reaction from AMD. Probably because it wouldn't apply cleanly to whatever they currently have. It's sad to see your customers having to fix your drivers. It's even sadder to see you ignore it.

ethbr0 3y ago
This is the greatest travesty of closed/open models, IMHO. I get exactly what happens -- devs are shipping their sprint pipeline internally, and pull requests or issues from the current open source head never make it onto their radar. This gatekeeps bugs visibility behind whatever PM is running sprint planning, which always leads to delivering what management wants instead of what users are dealing with. In complex, diverse environments, you're always going to have a myriad of bugs that are caused by a specific configuration. Absent a path to actually fix that, you end up with an enterprise-only product that's only stable in extremely specific configurations. And the greatest evil... you're also ignoring helpful reports of configurations where it's broken!