The weak points of D? If you want the high-level view by the project leaders what needs to be done, look at the vision document: https://wiki.dlang.org/Vision/

The weak points of D? If you want the high-level view by the project leaders what needs to be done, look at the vision document: https://wiki.dlang.org/Vision/2016H2 https://wiki.dlang.org/Vision/2016H2 D certainly needs more libraries, but which language doesn't? The currently available stuff is: https://code.dlang.org/ https://code.dlang.org/ Further stuff depends on what you would use D for. You describe yourself as a "Python programmer". Web development? In this area D is still weak. There is only one solid framework http://vibed.org/ http://vibed.org/ which does not officially support any SQL database (it has Mongo and Redis though). Personally, I think vibe.d is fine for micro services, but it is still a long way until it could compete with Django. I built a prediction market web app with vibe.d. It has hand-written SQL queries (should probably have used https://code.dlang.org/packages/hibernated https://code.dlang.org/packages/hibernated). I had to write Github authentication from scratch. There are few conventions, which is irritating if you are used to follow Django tutorials. You feel lost. That is my experience with D. Personally, I have no issues with the standard library like the ranter, but I assume I'm in the minority with that.