Screaming Penguin

I'm a relative newb to Git. I like it, but I'm sure I'm still missing a lot. Anyway, I recently had to work out a way to create remote tracking branches, because I like branches, and I want them backed up and shareable. Here's how I did it, in case anyone else might find it useful (or in case anyone can let me know what I'm doing wrong and improve my workflow). (Taken from Google Doc notes I made whilst working this out.)

---

Git is distributed, so there is no real “true” source. All repos are equal.

Just because Chuck hasn't posted it yet. WTG MOVL.

Recently saw this come up on Reddit. Dear Game People: STOP FUCKING THINKING LIKE IT IS 1987. While the rest of the world is finally moving to Scene Graphs for plain-old-apps, you people are writing code like it is 1987. I understand it is easy to think this way, but it is time to face up to the new world of multi-processor CPUs and dealing with concurrent state.

Love "A Platitude on Software Failure".

But don't kid yourself that the high-hanging fruits of the technology tree—strong AI, for example—will be made manifest by a society more excited by the Facebook social graph than by feeding its children.

The web vs native app thing is coming around again. Tim Bray has a great write up and object lesson in response to the buzz from TechCrunch and others. I thought I would sound off on this.

Now, I have written on this topic before, some five years ago. However, I was having a discussion with Kevin Marks on Twitter early this morning and I thought the topic bore revisiting. While those of us up early or late in the US were enjoying live discussion of the Federated Social Web conference the topic of Microformats came up. Kevin specifically pointed me to "Namespaces Considered Harmful" on the Microformats.org site. It is actually a good read, but it has a number of flaws. Outlining the arguments, lets look at the major topic headings:

A great discussion of what 'lean' means in the software world. This is a hard question. Let me start by talking about my current employer. We have started a ground up rewrite of the old system. Mostly because it sucks, both structurally and functionally, too badly to deal with. We are almost done. Old code: 322089 lines of Java. New code: 56136 lines of feature plus Java.

So aside from Charlie's new home Movl getting called by Ars Technica, "The most impressive Google TV demo," there was another big game story that was easy to miss.