phobos is failure

[Nick Sabalausky]

"Steven Schveighoffer" <schveiguy at yahoo.com> wrote in message 
news:op.vj5htul8eav7ka at localhost.localdomain...
> On Wed, 06 Oct 2010 03:31:19 -0400, Jacob Carlborg <doob at me.com> wrote:
>
>> On 2010-10-05 21:41, Steven Schveighoffer wrote:
>>> On Tue, 05 Oct 2010 15:10:33 -0400, Juanjo Alvarez <fake at fakeemail.com>
>>> wrote:
>>>>
>>>> My Lord, how is the migration of Tango to D2 going? The last commit I
>>>> saw on the experimental branch was pretty old.
>>>
>>> Look at who did it :) I think it's safe to say D2 for tango isn't going
>>> to happen any time soon, if at all.
>>>
>>> -Steve
>>
>> I think someone else has started to work on this in a different 
>> repository, I don't recall who it was though.
>
> Hm... there's nothing newer than a year in the branch directory of Tango, 
> and googling for D2 and Tango just comes up with newsgroup posts.
>
> I have reason to believe anyways that despite any effort, Tango won't ever 
> be D2 compatible.  This comes from experience of trying to port it.
>

IMHO, the primary reason for Tango has been eroding (at least for D2). As I 
always saw it, the whole point of Tango was that Phobos was basically 
early-alpha-level with practically no features, and no one actively working 
on it (just a little bit of occasional attention from Walter). In those 
days, Tango mage *perfect* sense. But Phobos2 has come such a long way, and 
has the added bonus of not leaving you lost in epic package/class 
hierarchies. I don't mean to bash Tango, I used it and loved it for a long 
time. I'm just not sure it's really needed on D2.

What I *do* think could be useful is a "Phobango" of sorts to help in 
porting D1/Tango to D2/Phobos. Thinks like mapping locate/locatePrior's 
interface to Phobos2, or Stdout.formatln("{}") to writefln("%s"), etc.