John Carmack a aussi dit dans une interview qu'il compte libérer le code du Doom Engine comme il a été fait avec tous leurs autres anciens moteurs et qu'éventuellement le moteur de Rage sera libéré lui aussi. Pour des raisons d'indépendance, id Software refuse d'utiliser des middlewares propriétaires qui pourrait leur empêcher de faire ce que bon leur semble avec le code.
A: I do take a great deal of personal pride and satisfaction with what I've been able to do with getting so much of the stuff out. Sometimes I think about it, and while I know it's not something I'm generally considered for, I may be one of the most prolific open source authors considering all the code that I've written over the last 15 years that I've made open source, or have made open source there. I do think it's very valuable. I'm very happy when I see both user gaming community stuff, or research universities, or people doing simulation tests, or bringing up things. Every new piece of hardware ends up having Doom or Quake titles used as an early form of test application. So I'm very happy to have done that. It's certainly going to continue. I mean I won't commit to a date, but the Doom 3 stuff will be open source. We still make those decisions even today when we're doing the Rage code when we have decisions about "do we want to integrate some other vendor's solution, some proprietary code into this". And the answer's usually no, because eventually id Tech 5 is going to be open source also. This is still the law of the land at id, that the policy is that we're not going to integrate stuff that's going to make it impossible for us to do an eventual open source release. We can argue the exact pros and cons from a pure business standpoint on it, and I can at least make some, perhaps somewhat, contrived cases that I think it's good for the business, but as a personal conviction it's still pretty important to me and I'm standing by that. http://www.linuxgames.com/news/feedback.php?identiferID=9374(...)
Pour rappel le code écrit par des tiers et propriétaire, c'est l'une des difficultés qu'a éprouvé Sun pour libérer Solaris, ainsi que des difficultés actuelles pour livrer une solution openJDK fonctionnelle où il faut boucher les trous des trucs qui n'appartenaient pas à Sun.
# Les moteurs d'ID
Posté par satan . En réponse au journal Le jeu Rage id software sortira sous Linux. Évalué à 10.
A: I do take a great deal of personal pride and satisfaction with what I've been able to do with getting so much of the stuff out. Sometimes I think about it, and while I know it's not something I'm generally considered for, I may be one of the most prolific open source authors considering all the code that I've written over the last 15 years that I've made open source, or have made open source there. I do think it's very valuable. I'm very happy when I see both user gaming community stuff, or research universities, or people doing simulation tests, or bringing up things. Every new piece of hardware ends up having Doom or Quake titles used as an early form of test application. So I'm very happy to have done that. It's certainly going to continue. I mean I won't commit to a date, but the Doom 3 stuff will be open source. We still make those decisions even today when we're doing the Rage code when we have decisions about "do we want to integrate some other vendor's solution, some proprietary code into this". And the answer's usually no, because eventually id Tech 5 is going to be open source also. This is still the law of the land at id, that the policy is that we're not going to integrate stuff that's going to make it impossible for us to do an eventual open source release. We can argue the exact pros and cons from a pure business standpoint on it, and I can at least make some, perhaps somewhat, contrived cases that I think it's good for the business, but as a personal conviction it's still pretty important to me and I'm standing by that.
http://www.linuxgames.com/news/feedback.php?identiferID=9374(...)
Pour rappel le code écrit par des tiers et propriétaire, c'est l'une des difficultés qu'a éprouvé Sun pour libérer Solaris, ainsi que des difficultés actuelles pour livrer une solution openJDK fonctionnelle où il faut boucher les trous des trucs qui n'appartenaient pas à Sun.