4 ms·

> AMD only managed to negotiate that because Intel lost in arbitration [1]. Intel's preferred option was always to eliminate AMD entirely. It's good for us cons

> AMD only managed to negotiate that because Intel lost in arbitration [1]. Intel's preferred option was always to eliminate AMD entirely. It's good for us consumers that they didn't succeed in that! OK? regardless of why or how it happened, it happened and it means that AMD is fine. If you knew that I don't know why you even mentioned it in the first place. > NVIDIA absolutely has an incentive to get rid of Nouveau. Its existence discloses IP (their GPU inner workings) that they would prefer to keep secret. Any articles to back that up? Seems counter to Nvidia offering support in publishing documents: https://en.wikipedia.org/wiki/Nouveau_(software)#History https://en.wikipedia.org/wiki/Nouveau_(software)#History > Another fun one: The FBX file format, which Autodesk makes money on through Maya, has a half-hearted attempt at DRM in it to limit it to approved Autodesk licensees. Blender's FBX exporter breaks it with a pass-the-hash attack. Get rid of that and Blender can no longer talk to Unity. Obviously, the entire industry benefits from the fact that Autodesk can't go after Blender for this. Again would love an article on this. I can't find anything backing up that this ever happened. Not only on Audodesk's website do they mention third party software but they have an SDK for this file format for others to use. While blender does in fact not use that SDK, and the format is proprietary, I can't find anything backing up what you claim.

pcwalton 3y ago
> OK? regardless of why or how it happened, it happened and it means that AMD is fine. AMD is only fine because Intel wasn't able to sue them out of existence. If Intel had managed to do in the 90s what Nintendo did to Yuzu just now, there'd be no Ryzen today. > Seems counter to Nvidia offering support in publishing documents NVIDIA only started publishing documents because Nouveau's success in reverse engineering meant that it was pointless trying to pretend that the genie could be put back in the bottle. Nintendo undoubtedly knows this too; lawsuits like this in 2024 ultimately aren't rational moves on their part, but big conservative Japanese companies have never been known to be particularly adaptable. > Again would love an article on this. I can't find anything backing up that this ever happened. Not only on Audodesk's website do they mention third party software but they have an SDK for this file format for others to use. While blender does in fact not use that SDK, and the format is proprietary, I can't find anything backing up what you claim. I found it myself when I was documenting the FBX file format (which I eventually gave up on because it was too horrifying of a format to motivate continuing) [1]. Blender calls it "CRC rules", but I think it's actually an attempt to lock non-licensees out. The SDK is closed-source, proprietary, and comes with a whole bunch of restrictions in its EULA. [1]: https://github.com/blender/blender-addons/blob/main/io_scene_fbx/encode_bin.py#L30 https://github.com/blender/blender-addons/blob/main/io_scene...

pcwalton 3y ago

> OK? regardless of why or how it happened, it happened and it means that AMD is fine. AMD is only fine because Intel wasn't able to sue them out of existence. If Intel had managed to do in the 90s what Nintendo did to Yuzu just now, there'd be no Ryzen today. > Seems counter to Nvidia offering support in publishing documents NVIDIA only started publishing documents because Nouveau's success in reverse engineering meant that it was pointless trying to pretend that the genie could be put back in the bottle. Nintendo undoubtedly knows this too; lawsuits like this in 2024 ultimately aren't rational moves on their part, but big conservative Japanese companies have never been known to be particularly adaptable. > Again would love an article on this. I can't find anything backing up that this ever happened. Not only on Audodesk's website do they mention third party software but they have an SDK for this file format for others to use. While blender does in fact not use that SDK, and the format is proprietary, I can't find anything backing up what you claim. I found it myself when I was documenting the FBX file format (which I eventually gave up on because it was too horrifying of a format to motivate continuing) [1]. Blender calls it "CRC rules", but I think it's actually an attempt to lock non-licensees out. The SDK is closed-source, proprietary, and comes with a whole bunch of restrictions in its EULA. [1]: https://github.com/blender/blender-addons/blob/main/io_scene_fbx/encode_bin.py#L30 https://github.com/blender/blender-addons/blob/main/io_scene...