Awesome job guys. I'm really digging this stack. It is giving me motivation to learn more about Backbone.js

I agree, I always end up hitting my 4GB limit with a VM open and Chrome with 12 tabs. Upgrading will be the next thing that I ask from the boss.

I just noticed it yesterday (or maybe the day before).

It is really a bummer when you are used to going to a website to use their feature and the feature isn't there anymore.

So I'm guessing that you are giving your bot a pub/priv key to get stats?

If you don't mind me asking what XMPP server are you using?

I'm guessing that this is a pretty powerful computer to run the emulator on?

I don't know what XMPP server we are using. I was not the one that set that up. I only have access to all of the FreeBSD/Linux machines in the company, someone else gets the pleasure (or should I say displeasure) of managing all of the Windows server infrastructure (AD, File servers, stuff like that), including where our XMPP service is being run because it requires AD access. Upsides and downsides to being the only developer in the company that knows Unix...

We have a gitorious server that also has a jenkins account (jenkins connects over SSH). It is running within a VMWare Virtual Machine with access to 4 cores running at 2.4 Ghz, and 14 GB's of ram. Whenever jenkins notices a change in git (using polling, every 5 minutes, set up for now, eventually I'll get around to doing push notifications of some sort ...) it pulls down the latest source code, and starts up the Google Android emulator (basically qemu for the ARM platform with the devices as an Android phone would have them), once that is started up it compiles the source code (java) and using adb installs it on the phone, runs the test suite, and reports any errors back, Jenkins then shuts down the emulator.

It isn't extremely fast, starting up the emulator takes about 50 seconds or so, and I am trying to get a faster server to use as a jenkins build slave, but for now it works wonderfully. Everything I mentioned is completely managed by jenkins.

Anyone know what machine he was using? I guess it was some SGI machine but it didn't say the exact model.

Not sure about the machine but according to Romero[1] Quake (as with Doom) was developed on NeXTSTEP 3.3, which they continued to use, later running on Intel hardware, until 1996.

QuakeEd on NeXTSTEP: http://rome.ro/uploaded_images/qe_dev-726646.gif

[1] http://rome.ro/2006/12/apple-next-merger-birthday.html

Would that have been running NT back then, perhaps the MIPS version?

The environment does look like Visual C of which 1.0 came out somewhere in the 94-95 time-frame if I'm remembering it correctly, though it might have been just a tad earlier.

I bought one of these machines around that time for a design company I was interning at. It's an Intergraph, obviously I have no idea which model. These machines were built to order, so it could have anything in there. That multimedia keyboard brings back memories, prolly the worst $100 I ever spent.

This machine would be running WinNT 3 or 4, most definitely not the MIPS build.

Probably Intergraph.