[Profan]

I wish standardizing documentation tooling (everyone uses a different tool today and ddoc by default has _no_ styling, no navigation, no nothing, so usually nobody writes docs for their code unless it's a big project like vibe.d) and IDE support was on this list (vscode centric tools exist and mostly work, but it's still fairly hit and miss) .. D's tooling has languished for a long time even if it is a great language otherwise.

[destructionator]

I've been working on that with my dpldocs.info site. Dub packages get linked to it automatically unless they manually override (which I didn't want to allow in the name of standardization but got overruled :( )... but like tons of things are still just plain missing docs and nothing I can do about that automatically.

We are considering hurting their search result score based on doc coverage tho.

[EvenThisAcronym]

Visual D with Visual Studio is the gold standard, with full debugging, autocomplete, and static analysis support.

Code-D with VS Code is also great, and it has fairly recently gotten funding from the D Language Foundation for further development.

There's also DCD, D-Scanner and dfmt which can be used with a lot of different editors.

[1980phipsi]

Also, what's the difference between code-d [1] and dlang-vscode [2]

[1] https://marketplace.visualstudio.com/items?itemName=webfreak...

[2] https://marketplace.visualstudio.com/items?itemName=dlang-vs...

Edit: It seems that dlang-vscode recommends to instead use vscode-dls [3] or code-dlang.

[3] https://marketplace.visualstudio.com/items?itemName=LaurentT...

[1980phipsi]

Do either Visual D or Code-D work with Linux or WSL? It would be really nice to have the GUI for debugging linux code. Some libraries are just much easier to get set up in linux.

[aldacron]

Visual D is a plugin for Visual Studio, so no. Code-D is a plugin for VS Code, so it works anywhere VS Code does.