As for use cases, command line is a good bet. I suggest starting with something that has a clear scope and isn't chosen based on a marketing feature. For example if you're going to build a server of some sort be sure the project won't grow and require database access (or verify that the bindings you'll need are up-to-date beforehand), and while making use of const/pure would good to use don't make your design choices around it. Do expand/explore and contribute, real world testing needs to be done, but be genital with it as things are still coming together and you want to show a productivity gain and quality.
I'll keep it in mind. Why can't I make design around const/pure?
************************************************************************
Do you know any famous company or software publicly running on D? I searched at StackOverflow, Wiki4D and Wikipedia without meaningful results.
2012/2/9 Jacob Carlborg
<doob@me.com>
On 2012-02-09 02:13, Adam D. Ruppe wrote:
The way I do it is to try updates at some
point when I have a little free time.
Get the new version, but keep the old version.
Compile. If it works, sweet, probably ok to keep
it.
If your app doesn't compile, and it isn't an
easy fix, just go back to the old release.
Every two or three releases though, I'll take
the pain and make sure I'm up to date anyway,
usually because the new dmd releases are good
stuff.
--
/Jacob Carlborg