On Tuesday, 5 January 2016 at 12:27:12 UTC, Ola Fosheim Grøstad
wrote:
I wonder what kind of programming people plan or _hope_ to use
D for in 2016?
Do you have plans to:
1. migrate legacy C++ code bases to D when C++ bindings are
final?
2. integrate with numerical solutions like TensorFlow?
3. create web services with vibe.d?
4. run D apps in the cloud?
5. run D apps on mobile?
6. create runtime less programs (games, embedded)?
7. work on the D language/phobos ?
8. or something else?
In 2016 I planned to use D to replace some parts of our large
monitoring system (Python-based "graphite" metric storage and
visualization tools). What I needed was:
1. Language quality - perfect.
2. Fast numeric processing - perfect.
3. Easy deployment - not ok: there is no system-wide packaging
for D libraries (I'd like to see debian .deb's for most D
third-party libraries, or at least something like 'pip' for
python). Correct me if I'm wrong but dub can't deploy system-wide.
4. Lack of some important for me libraries with D-way API (not
one-to-one C-wrappers). But this is improved during last year.
5. Easy development - not ok. Correct me if I'm wrong but still
no stable support for debugging - demangling problems for OSX out
of the box (not sure about Linux). No good plugins for most
popular IDE.
6. Lack of some standard libraries - namely libasync. When I use
library for my app, which I hope to use for years, I'd like to be
sure that library development will not rely on single person
motivation, spare time availability, etc.
So, during 2016 I was not ready to use D in production.
In 2017 I hope to see better progress in D weak areas. I hope to
continue to contribute to D community and language, and use it
for my personal projects.
What other languages do you think you will use or toy with in
2016 and for what purpose?
What would it take for you to use D instead, or what changes
would be needed for you to move from language X to D?
