Just for starters:

http://hg.icculus.org/icculus/aquaria (official repository, with post-Humble Bundle patches from several people)
http://bitbucket.org/_Agent/aquaria
http://achurch.org/cgi-bin/hg/aquaria

(Not to say the others aren't undergoing development as well; Aquaria is just the only one of those four that really captured my interest.)

Append "&nfpr=1" to the search URL. If you use keyworded bookmarks in Mozilla: http://www.google.com/search?q=%s&nfpr=1

As long as we're talking test runs, the Chuo Shinkansen hit 581km/h in 2003.

Interesting you should mention this; I've had the same problems you describe trying to get CMake to cross-compile, but with autotools, "--target=other-cpu" has generally worked fine in my experience (making it just about the only redeeming feature in that spaghetti mess of shell and m4 code). Admittedly I haven't tried building an entire Linux distribution, so maybe I just happened to choose packages that don't rely on running test programs, but IIRC autotools will explicitly disable the standard runtime tests when cross-compiling.

is that it's got ugly syntax, effectively no cross-compiling support, and less-than-helpful documentation. And its generated Makefiles sometimes miss changes in header files, forcing you to "make clean".

But yeah, it's still a good alternative to autotools.

That's 62 miles, or 100km. I can't recall hearing about a 100km jam in the 11 years I've been here, though I'll grant you a few 50-60km jams pop up on the news most holiday seasons.

From TFOpinion (page 33):

So if you're in one of those states, it looks like the answer is yes, it's illegal to plant a GPS tracker if you're not law enforcement (and sometimes even if you are law enforcement).

(And why does Slashdot still not support Unicode?)

It's the beer glasses set on top of it that make the ring.

I wouldn't call it a generation "clash" so much as a "progression" from one generation to the next. As one who's been programming for a fair number of years, I certainly advocate knowing the details of what's going on at the lowest levels; if you're not familiar with how caches work, for example, you might have trouble figuring out why a loop over a 2-D array is running so slowly (answer: you have the loops inverted, so every array access is missing the cache). For those who have learned programming in more modern environments, I hope my column has been informative. But at the same time, if your target environment has the capability to take care of all the details for you, I see nothing wrong with taking advantage of that. If your PC can generate new kittens faster than STL kills them off, then by all means, blast those felines to bits. (: After all, that's the whole point of progression in computer technology -- to let the programmer focus more on the high-level problem and less on the low-level nuts and bolts.

Also, just in case it wasn't clear from the column, it was not at all my intent to criticize the original software. There are certainly things that I would have done differently, but in my own playthrough, the game ran nearly flawlessly in its target environment. Creating a complex piece of software like this is no small effort, and I have nothing but respect for Alec (Holowka, the developer) for completing his work to such a high caliber.

Just for the record, this PSP port is totally unofficial -- I did it mainly for the challenge of porting (and because I enjoyed the heck out of the game). That said, judging from the Wii's specs, I don't think a Wii port would be too difficult as long as you don't have to copy textures into GPU RAM for drawing. The Linux port uses SDL and OpenGL, so if there's a functional SDL/GL port for the Wii, that could save a lot of time.

I wasn't the one who posted the story, but I added a Coral Cache redirect for Slashdot referrers after the Wolfire column went live (just in case -- even though we all know Slashdotters never RTFA). People who actually want to clone the repository will presumably know not to use the Coral Cache URL, people who are just browsing shouldn't notice a difference, and hopefully my server will survive the onslaught. (:

Of course things are going to go wrong. They in fact succeeded at their primary objective, which was to run the ion engines for 1,000 hours; everything beyond that is a bonus. If anything, the engineers involved ought to be praised for being able to work around all those problems and get the thing back to Earth.

We tried that when they released the slim PS3 without Other OS support ("don't worry, they won't take it away from current PS3s"). Look how that turned out.

Seriously, that may be the best solution. It's what I ended up doing in a similar situation recently, because everything I could find was either 1: too expensive, 2: not cross-environment compatible (Sharepoint), 3: not stable/secure/reliable (many open source projects), and/or 4: difficult to use (just about everything -- in fact, they had used Sharepoint for a while and were desperate for anything else).

People like to talk about the virtues of software reuse, but they rarely mention the downside of accumulating complexity as a single program tries to do more and more -- or of attempting to force users into a single mold in order to limit complexity. Particularly when it comes to content management (and the intricacies of traditional version control systems versus the desire of non-technical users to just Get Things Done), if you consider the running cost of user support, it can sometimes be more efficient to build custom software that does exactly what you need, the way you need it to.

Bleah. That was embarrassing. (Though maybe it indicates why I'm good at programming -- I tend to read things literally...)