This looks lovely: the right balance of editor-as-environment (ie: multiplayer level-building, which people recognise from Minecraft) with scripting, full control, and a learning curve. Really need to poke this.

"I wanted to compile a list of online, Web-based tools that Web engineers can use for their work in development, testing, debugging and documentation." It is a really good list (I say this mainly because the first thing on the list is RequestBin, which is the thing I always forget the name of).

"jq is like sed for JSON data – you can use it to slice and filter and map and transform structured data with the same ease that sed, awk, grep and friends let you play with text." Sounds super-useful.

"My interest in materials… is like my interest in tools. What can be made with this? What can this do that other materials cannot? Materials with special properties are cool because they can open new possibilities in manufacturing, design, or even behavior. Additionally, they’re such an amazing cultural artifact. Where and how something gets made says so much about us as people, as a species, even. In a beautiful fabric, the simplest thing can be magic."

"I spend every day writing Rails code in vim, and I’ve optimized the heck out that process. The screencast contains the best of what I’ve learned for creating and editing Rails code at top-speed. Come look over my shoulder and I’ll show you my best stuff." Might give this a pop at some point.

"The (for now) final end product seems incredibly obvious. And popular.

Yet it took decades of iterative innovation, from some of the cleverest minds in the field, to make something so apparently simple yet powerful.

And every step was astonishing." This is great stuff from Francis.

"So, as some of you may know, the old shrine got re-activated as a working shrine a few days ago, and the Church classroom cleared away for meditation and contemplation, led by Fa Zang (Rinpoche), the guy in the buddhist monk robe who has been doing a lot of sewing in the craft area recently." I love mailing lists. And this is a remarkable post.

"Using vim is like talking to your editor in ‘verb modifier object’ sentences, turned into acronyms." Which is a good way of thinking of it.

"Calepin reads Markdown-formatted, plain-text files stored in your Dropbox and converts them into blog posts for you." Which is pretty clever.

"A photograph has to be rational. It has to be rational in itself. It has to be rational and complete. … it is the illusion of a literal description of what the camera saw. From it, you can know very little. It has no narrative ability. You don't know what happened from the photography. You know how a piece of time and space looked to a camera." As usual, I'm reminded how much I love Gary Winogrand.

The ninth day of the Hindu Navaratri festival, the "Worship of Implements", where "weapons are worshiped by soldiers, and tools by artisans"; "In the cross cultural development that has revolutionized the society, with modern science making a lasting impact on the scientific knowledge and industrial base in India, the ethos of the old religious order is retained by worship of computers and typewriters also during the Ayudha Puja, in the same manner as practised in the past for weapons of warfare."

Jon is smart, and one of the best writers of interactive fiction (in all its forms) that I know. So I am looking forward to this.

"The easiest way to share localhost over the web." Very nice. Smart pricing model, too.

"One succeeds because it leverages the player's motivated, explorative, self-driven experience; the other fails because it relies on a hackneyed, disjointed "epic" plotting (told in 3 separate plot-lines via cutscenes) with incongruous settings and 2-dimensional characters. One succeeds because its formal systems directly feed the player's connection to the world and characters; the other fails because its formal systems bear no discernible relationship to the stories the game wants to tell." This is strong stuff from Michael; I am increasingly fed up of the focus on (poorly-told) stories in games.

"Know that there are no "accidents" in this game design. Everything you notice about the game, and every subtle interaction that you experience, is intentionally packed with meaning." (Gravitation, still, being my favourite of Rohrer's games, I think).

"Crucially, Goodrich entreats the public to note the following: "this change should not directly affect gamers, as it does not fundamentally alter the gameplay." This one statement should cause considerable distress, as it suggests a troubling conclusion about Medal of Honor as a work of public speech.<br />
<br />
To wit: it suggests that the Taliban never had any meaningful representation in the game anyway. If a historically, culturally, and geographically specific enemy can simply be recast in the generic cloth of "opposition," then why was it was called "Taliban" in the first place?<br />
<br />
And if the Afghan war in which the new Medal of Honor is set was one explicitly meant to drive the Taliban from their strongholds in Afghanistan, why should it matter that the game is set in that nation in the present day at all? In short, how was this Medal of Honor title meant to be a game about this war in particular?" This is a marvellous, critical piece of writing from Bogost.

Nice post on Awk basics – most of which I knew, but the examples are still great, especially those involving variables. The links out to the Hacker News and Reddit threads are also full of good stuff.

"By decoupling their data to minimize exporting, they said their polish actually became fun, not to mention efficient. I think many projects would benefit from finding a way to similarly decouple their tunable data." Yup.