Re:How to program independent games (Johnathan Blow of Braid...
by chipsy on Wednesday August 10, 2011 @06:12AM
(#2867529)
A lot of game code is actually "data" code, so the large functions come about naturally because so many assumptions and special-cases are made that you don't have anything resembling a CS-style algorithm, just a blob of "integrated assets" - and so the only route for further progress is a new syntax tailored towards the particular methods of integration being addressed.
That said, a new syntax can work, if it's the right one.
Re:How to program independent games (Johnathan Blow of Braid...
by felipemnoa on Wednesday August 10, 2011 @01:48AM
(#2866940)
I think he was talking on the extreme.
One idea that I don't think fits for the type of system I develop is the idea of preferring huge blocks code over function calls (around 30:00). He counters the benefit that the function name documents the chunk of code it encloses, but an even bigger benefit, in my opinion, is that the function signature documents the function's inputs and outputs. If you avoid global variables then you know when you modify a function exactly what information you have access to and exactly what information the function produces. This makes changing the function much easier.
He says he's talking about thousands of lines of code that always get executed in serial, so it doesn't sound like my code is very similar to the code he's talking about. I also expect that code I write gets read and modified much more often than the code he's talking about.