-
- Already a Member? Login
midpipps Mar 15, 2010, 10:40 pm
Some really interesting ideas in there. Could probably get more out of it with the audio. But it still got me thinking.
cmoidel Mar 16, 2010, 7:45 am
I was one of many that disappointingly got turned away at the door. Thank you for posting the slides online. I look forward to reading them. Do you know if the "GDC Vault" is going to have audio or video for your presentation? I was told that only some talks were recorded.
Vortex646 Mar 17, 2010, 1:06 am
Almost hard to understand xD
Fersis Mar 17, 2010, 9:49 pm
While i agree with the 3, 'Code designed around a model of the word' is the most important (Since it affects much more than code)
Great read.
Great read.
gha Mar 24, 2010, 9:57 am
hi
the last part and the examples are hard to understand. I think that you are right, but the problem is bigger and the programming community (not only game programmers) are full of vicious. First OOP isn't well suited for a data driven approach because the code and the data are 'mixed' in the same place (classes) and in a more orthogonal language (like C ou Go) you can think about the data first and then think about the code. when you define all data structures the code comes naturally.
The excess of abstraction is nocive too, a lot of design patterns can be avoided using more simple solutions. I remember an old demo with sourcecode from Crytek about normal mapping (the demo was published in some shaderX series), to use the code and call the function that calculate the TBN matrix you must use proxy pattern, why create thousand of classes if you can instead create a simple array ? Its only an example, a lot of code from software (game) industry is over-complicated.
the last part and the examples are hard to understand. I think that you are right, but the problem is bigger and the programming community (not only game programmers) are full of vicious. First OOP isn't well suited for a data driven approach because the code and the data are 'mixed' in the same place (classes) and in a more orthogonal language (like C ou Go) you can think about the data first and then think about the code. when you define all data structures the code comes naturally.
The excess of abstraction is nocive too, a lot of design patterns can be avoided using more simple solutions. I remember an old demo with sourcecode from Crytek about normal mapping (the demo was published in some shaderX series), to use the code and call the function that calculate the TBN matrix you must use proxy pattern, why create thousand of classes if you can instead create a simple array ? Its only an example, a lot of code from software (game) industry is over-complicated.
macton Mar 27, 2010, 5:58 am
@cmoidel Apparently video is available in the GDC Vault. I'm told some people have watched it.
macton Mar 27, 2010, 9:29 am
@cmoidel Apparently video is available in the GDC Vault. I'm told some people have watched it.
