Gaaah! Almost forgot to write the newsletter on time again. Been busy, you see, with yet another coding project (still unrelated to games). Though who knows — the ability to focus on writing your game as opposed to wrangling your tools is increasingly important these days, so simplicity matters a lot. I’ll keep you informed.
This week @JuhanaIF points us at a postmortem of 80 Days that does a good job of relating the difficulties of making such a big game. And while on the topic of interactive fiction, Hardcore Gaming 101 gets around to reviewing Fallen London. A good way for me to see what has changed since I stopped playing… and what hasn’t.
Of direct interest for developers is this article on architecture in videogames. Once again it turns out that in order to make games (or, indeed, any software) it’s more important to know about the real world than programming. In this case history, geography and materials. And you know, I’m hardly an expert myself, but I find it baffling and worrying that an educated person today doesn’t know why the compass points matter when building a house. Are we so deeply invested in the myth that we have somehow “conquered nature”?
Last but not least, the Wall Street Journal is running a piece on how videogames are saving the symphony orchestra. Amusingly, they write about videogames as if we were still in 1985 (which says a lot about the kind of people they allow to make decisions in the newsrooms). But otherwise, it’s good to know that games have found yet another way into mainstream culture; I remember years ago when symphonic orchestras were arranging music from famous movies such as Star Wars or James Bond and thinking how cool that was.
Culture is culture, and that’s awesome. See you next week.