Within your circles is there any excitement at all among developers to work on Nintendo hardware? More specifically the Wii U? If you are able to give one based on your NDAs, I would appreciate a frank and honest answer.

Wow, I like this thread.

Being no hardware/software expert, one question has always got into my mind: the framerate matter, where do you have to put more effort in to get it higher and at what cost? I don't know if I have explained myself well, but I'll use an example: Mario Galaxy and Super Smash Bros Brawl have both a steady 60 fps that is noticeable. If the developer decided to use the 30 fps instead, what other parts could be improved? Or is there no relation whatsoever and that is all a question of working harder? I have never seen any good explanation regarding that matter. Finally, I still don't know if I made myself clear so sorry if not.

I work on engines, particle and physics, from porting engines to writing them from scratch.

My education.. well, I was in MIT the year the PS2 launched, and working for a large aerospace company for a few years then.. well i wrote it out but deleted it, if someone who knew me read it i would be found out in minutes.

I got into programming when i was a kid, copying programs out of a C64 magazine named Input, as such it has always been more hobby than job for me, so i am not the best person to ask for recommendations to becoming a developer, chances are those that will be one, always were from childhood.

Not answering the other questions for obvious reasons.

What are the three indie games you look forward to on ps4?

Anything huh?

As a web developer, I can relate. Luckily in my case I can play games, I also go climbing and read comics. What are your 'escapes' from computers?

There is some, but game creation is basically a case of will the publisher be paid for the game (will it sell), if the answer is no, unless you can finance it yourself, you dont work on a game.

As above, it isnt the difficulty, its the payoff, it isnt worth the studio time and money if the return is going to barely break even or not at all.

Its not as complex as you think, you make a game and it runs as best it can based on the hardware, the more detail you use the more power is needed, if that power isnt there you have to cut corners where possible to get it to run as best you can, that results in either dropping the resolution to decrease the demand on the system, or if theres no hope for 60 frames, simply deciding to work under the assumption that youre aiming for 30 frames.

If you throw up the prototype and its barely playable, you optimize and scale things back till it is, and go from there.

If 60 frames looks doable, thats what you aim for, if 60 frames is only achievable at too much cost, its 30 frames - then its a cat and mouse balacing act between getting it to look as nice as possible, at 30 frames, if that means dropping resolution then so be it.

Currently? you may laugh but I am in the process of getting a PHD in cancer genetics.

Side note Nintendo fans, bug Frequency, shes the one working on WiiU games at the moment.

Goddamnit man!

Laugh? Dang sight more impressive than my things. Good luck to you, sir.