What's the current state of D?

[Jason House]

Ameer Armaly Wrote:

> 
> "Walter Bright" <newshound1 at digitalmars.com> wrote in message 
> news:gua3u3$19c1$2 at digitalmars.com...
> > Ameer Armaly wrote:
> >> Yes. This is the showstopper for me and what caused me to quietly walk 
> >> away from D to begin with. In my opinion the fact that having two 
> >> runtimes is not only tolerable but acceptable as normal has and will 
> >> continue to hurt D1. We have Phobos, the "official" runtime and then we 
> >> have Tango, the "community" runtime. Moreover having two runtimes casts 
> >> doubt on the state of D as a whole; if we can't even decide on a uniform 
> >> runtime then people will wonder what other unknown traps of 
> >> incompleteness are in store. The fact that nobody bothered to work all 
> >> this out makes perfect sense- it's a lot more fun to be hashing out new 
> >> features- but if we intend to gain some semblance of mainstream respect 
> >> then it will be much easier with a single robust runtime.
> >
> > It has been bashed out for D2. Doing such changes to D1 will break 
> > everyone's D1 code, which destroys its mission of being stable.
> Really? I was under the impression that Tango will be ported to D2 to 
> continue the battle of standard libs but if I'm mistaken, then it's a lot 
> better than I originally figured. 

The druntime project is mostly a port of the Tango runtime to D2. On top of that, Don has ported the Tango math stuff to D2 Phobos. The stage is set for D2 Tango to be smaller and be installed alongside Phobos in D2.

There really is only three reasons I'm aware of that stop D2 Tango from existing today:
1. There is no practical way to write code that compiles with both D1 and D2
2.  There are bugs that limit how easily Tango can be ported to D2
3. D2 is a moving target

I've volunteered to fix D2 Tango when #3 is an issue, but that's not enough to make D2 a reality.