3 ms·
I worked with a guy like you once. He got fired. Three guesses why. For most game development, the code is written and compiled on PCs and then shipped to a de
by bitwize 10y ago
I worked with a guy like you once. He got fired. Three guesses why.
For most game development, the code is written and compiled on PCs and then shipped to a development version of the console hardware for testing. Naughty Dog in particular had a way of "live coding" their games in a Lisp dialect and shipping individual compiled functions to a running game instance on the PS2 dev box.
You think the demoscene kids can't match that?
Besides which, today's PCs have CPUs with sixteen (64-bit!) GPRs, GPUs and audio chipsets that vastly exceed the capabilities any Amiga had, gigs of RAM, and cutting edge development tools that the Amiga never had on its best day. I could be the biggest Jay Miner fanboy ever and I'd still write all my Amiga software from the comfort of a Linux PC.
- ekianjo 10y ago> For most game development, the code is written and compiled on PCs and then shipped to a development version of the console hardware for testing. When doing cross-compilation, is there a way to know if your cross-compiled code is as efficient/fast as code natively compiled on the target architecture ?
- bitwize 10y agoA cross-compiler can generate the exact same code a native compiler can. If you have a powerful development box, it will compile much faster than if you compiled on the native architecture. So there's that too. The NES probably couldn't run an assembler that could assemble a large program at all. NES games were developed and assembled on Unix workstations and wired to the console via an in-circuit emulator that simulated a NES cart.