D Conference Tango Phobos

[BCS]

Bill Baxter wrote:
> Jascha Wetzel wrote:
> 
>> Sean Kelly wrote:
>>
>>> Well, the first issues to address are the few incompatibility points 
>>> between Tango and Phobos within the runtime, the most visible being 
>>> Object.toString in Phobos vs. Obejct.toUtf8 in Tango.  This likely 
>>> means toUtf8 in Tango will have to change to toString, so if anyone 
>>> absolutely hates the idea, you're welcome to say so :-)  However, I 
>>> suspect there is a quiet majority using Phobos, so even valid 
>>> arguments against the way it does things may have to be ignored if 
>>> the change would break some user-visible portion of the Phobos 
>>> library.  Suggestions here are welcome also.
>>
>>
>> ridiculously, the only reason i can come up with, that kept me from 
>> using tango in programs that don't use networking, is the verbose 
>> string formatting syntax (i don't want to start a discussion about 
>> which one is better. i consider it a matter of taste).
>> when tango and phobos will co-exist painlessly, i'll probably be using 
>> std.stdio, std.format and everything else from tango :)
> 
> 
> The only thing I really use consistently from Phobos that I actually 
> *like* using is std.stdio.  The thought has occurred to me a few times 
> that Tango would be much more attractive to me if it only had writefln.
> 
> I tried Tangobos but it states pretty clearly that it's not intended as 
> a long-term solution, and that you are expected to use it as a 
> transition crutch as you finish porting your code to pure Tango.  But I 
> don't *want* to get rid of my writefln's.  I *like* them.
> 
> I thought maybe I was the only one with such irrational attachments, but 
> it seems I'm not alone.  :-)  If that's the case then hopefully someone 
> will make a port of std.stdio to Tango at some point.  That makes more 
> sense to me than everybody rolling their own as Sean suggests.
> 
> --bb


Maybe Tango and phobos could become two parts of the same lib. Phobos 
would be a collection of light weight modules with free functions and a 
few classes (with very simple hierarchys) that "gets the simple stuff 
done". Tango would the the Big brother side with lots-o-functionality.