Prioritizing bug fixes & improvements to D

[Downs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jarrett Billingsley wrote:
> "Walter Bright" <newshound1 at digitalmars.com> wrote in message 
> news:fasudc$1mvc$1 at digitalmars.com...
>> The problem is, forward references also have a high cost to fixing.
> 
> They also have a high benefit: the compiler will no longer give errors (that 
> are impossible to workaround without serious redeisgns) on otherwise valid 
> code.
> 
> Furthermore, delaying issues that are difficult to fix means they will never 
> be fixed, at least not on any reasonable timescale.  You know that with all 
> the new features you're going to be introducing that there will be tons of 
> bugs, probably lots of little easy ones.  Keep squashing all the little 
> ones, though, and the big ones will just fester.
> 
> Another one that comes to mind is broken selective/renamed import privacy 
> (bugzilla 313/314).  These are not minor issues, and if they take a lot of 
> time to fix -- so be it.  I'd be happy to wait another couple of months for 
> all the cool new D2 features. 
> 
> 

Strongly agreed. Granted, part of it is because I'm on GDC, but even so,
I'm regularly surprised how unstable stuff is, especially when you start
prodding corner cases. I'd choose a reliably-working 1.0 over a nice,
but borked 2.0 anyday.
Just my ¢2. --downs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG0wxrpEPJRr05fBERAu9oAKCj9IBiXsszGqSE+12ct1xFeKHXqwCgoSg2
OyEznmWWGt+g088IDH721nE=
=3jUE
-----END PGP SIGNATURE-----