I'm only supporting D2.
D1 support would require more effort that can be better used
to add more features and create more libraries. New D users are
unlikely to try D1 since D2 is now rather stable, and even if
the do, they won't stay there for long.
I myself started using D with D1 about 1,5 years ago, then 6
months ago I moved to D2 and found it to be getting much more
stable over time.
For a new D2 user, D1 libraries basically don't exist; if half of
the libraries are D1 only, it seems there are only half as many
libraries.
On Saturday, 21 January 2012 at 16:07:58 UTC, Stewart Gordon
wrote:
For the last however long, I've been still programming mostly
in D1, but aiming to keep my libraries compatible with both D1
and D2.
But changes in D2 have made this more of a challenge. I've
also been put off switching to D2 by the wait for D1 to be
finished.
Now the plan to discontinue D1 at the end of the year has been
announced. And I'm wondering what to do with my libraries.
How many people here are still using D1?
What are those of you who write libraries mainly doing?
(a) supporting only D1?
(b) supporting only D2?
(c) releasing separate D1 and D2 versions?
(d) using versioning to support both with one set of code files?
If practically everyone's using D2 now, maybe I'll migrate my
libraries to it. If, OTOH, there's still real demand for D1
libraries, I'll continue to support D1. I might have to see
how supporting D2 as well works out. It seems I'll have to
abandon the idea of keeping the code compatible with the D spec
as of DMD 1.00. It seems the reasons for doing this never
happened anyway, and there doesn't seem to be an equivalent
milestone in D2.
Thoughts?
Stewart.
