phobos

By converting more of Phobos to being algorithms, they become agnostic to whatever allocation method is used.

Eventually these issues were ironed out and an improved Phobos became the standard library, with Tango made compatible with it.

Look at the gravity on phobos and demios which are way smaller than this thing.

There is also problem with Phobos vs Tango - where Tango is clearly and measurably better, but that thread of issues leads to leadership drama.

The Phobos vs Tango thing put me off too.

What if this star was responsible for ripping Pluto away from a planet or sending Phobos down into the inner solar system to be captured by Mars?

@nogc is still a new addition to the language and phobos is not fully flagged with it.

Getting to the surface and back would be a bit of a problem, but a SpaceX/Bigelow team could possibly land on Phobos and return in the next 5 years.

In addition to writing code for the std.* Phobos library, I think Andrei has been using D for data processing stuff related to his recently finished dissertation.

I've tried several times to write a project in it, and every time I found some horrible bug, something missing, broken (OSX support is poor) or libraries turned out to be useless/outdated (dsource is a graveyard), or that I've chosen the wrong set (D1 vs D2, Phobos vs Tango).

As aside: I just discovered that the language authors are converting the std library (phobos) to be "no GC".

The post was inspired by Saturday's playthrough of "Leather Goddesses of Phobos" - one of the few Infocom games I hadn't spoiled for myself in my youth, due to Activision's decision to omit it from the "Lost Treasures" collections.

In my opinion the fact that there were two competing standard libraries (Tango and Phobos) certainly brought confusion and needlessly fragmented the community.

The D standard library (aka Phobos) doesn't suffer these limitations.

The standard library (Phobos) is open source.