Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Well, the general recommendation for any language is to not rewrite an existing code base. Writing new code or converting portions, where bugs need fixed, can be a good strategy.</p> <p>The quick and dirty replay: If you have to ask, you shouldn't be using D in production yet.</p> <p>Some don't consider D to be an improvement and others think it will remain in the "spheres of irrelevancy." Looking at its history shows that it has what it takes to survive.</p> <p>Personally if I were to pitching the idea of having production product using D I'd probably consider:</p> <ul> <li>Team size. How many developers need to be educated on D in the early stages to its completion.</li> <li>What libraries will be needed and would we have the time and man power to build or wrap a library.</li> <li>Would we be able to handle patching bugs in libraries used.</li> <li>Would an architecture be need that isn't supported by DMD</li> </ul> <p>These are concerns which will be part of any discussion especially for a young language like D, which has even broken compatibility with existing libraries making it only about 4 years old (and still survived). I don't use other compilers so not having support from DMD would be concerning, the history of the other compilers isn't stellar and it is good to have the knowledge there could be another compiler to fall back on. Of course if you have a crew that could maintain a compiler...</p> <p>I think D can be used in production, but is something that should probably be very controlled. You'd want someone familiar with D on a team that is going to be making a production product with it, for now.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload