I find DLS [1] to be very stable, updated more often [2], and it just works without issues (vs. Code-d)  ~~ at least for me. I think we should give it a chance.

I created a long list of features [3] I'd like to see in D IDE. Hopefully some of them is being worked on.


[1]: https://marketplace.visualstudio.com/items?itemName=LaurentTreguier.vscode-dls
[2]: https://github.com/LaurentTreguier/dls/blob/master/CHANGELOG.md
[3]: https://github.com/dlang-vscode/dlang-vscode/issues/53

On Wednesday, 8 August 2018 at 07:25:57 UTC, Tab wrote:
> I find DLS to be very stable

Ironically, as the developer of DLS, I'm not sure if it should be considered as stable. I've had quite a number of crashes myself, sometimes even seemingly right at startup :/
Although the latest version does fix a crash that was happening during garbage collection, so now it might be more stable.
(Fun fact: since garbage collection always happens at least when the program exits, it was technically crashing 100% of the time before)

> I created a long list of features I'd like to see in D IDE. Hopefully some of them is being worked on.

I have some things to fix first, but they will be worked on at some point; finding all references to a symbol especially is something that interests me.

On Wednesday, 8 August 2018 at 07:57:49 UTC, Laurent Tréguier wrote:
> On Wednesday, 8 August 2018 at 07:25:57 UTC, Tab wrote:
>> I find DLS to be very stable
>
> Ironically, as the developer of DLS, I'm not sure if it should be considered as stable. I've had quite a number of crashes myself, sometimes even seemingly right at startup :/
> Although the latest version does fix a crash that was happening during garbage collection, so now it might be more stable.
> (Fun fact: since garbage collection always happens at least when the program exits, it was technically crashing 100% of the time before)
>
>> I created a long list of features I'd like to see in D IDE. Hopefully some of them is being worked on.
>
> I have some things to fix first, but they will be worked on at some point; finding all references to a symbol especially is something that interests me.

Code-d overcomplicates things I find though. I can't even build it, there's so many dependencies attached to it that it isn't worth looking through to even find which one is causing the build issue. Let alone there's a restriction that it can only build 32-bit. Also can't be built with LDC2 cause of the dependencies is trying to build a 64-bit binary even though the arch is set to 32-bit. It's a mess. DLS took no time at all to build, nice and simple. Just one thing is installing the extension didn't create that symbolic link for me. And the plugin just silently passes an empty path if it can't find DLS.

https://github.com/LaurentTreguier/vscode-dls/blob/master/src/extension.ts#L20

On Wednesday, 8 August 2018 at 20:56:51 UTC, tide wrote:
> DLS took no time at all to build, nice and simple.

The only thing built is a small bootstrap program that downloads a prebuilt binary release, that's why it's fast. Before v0.5.0, DLS was always compiled, and that took some time, as well as 3 GB of your RAM...

> Just one thing is installing the extension didn't create that symbolic link for me. And the plugin just silently passes an empty path if it can't find DLS.
>
> https://github.com/LaurentTreguier/vscode-dls/blob/master/src/extension.ts#L20

That's weird. What OS are you using ? There was a bug at some point with symlink creation on Windows, but it should be fixed now. For some reason it takes a crazy amount of time instead now, 30 seconds for a simple symlink...
If you have more info about this, you can always post an issue:
https://github.com/LaurentTreguier/dls/issues

On Wednesday, 8 August 2018 at 07:25:57 UTC, Tab wrote:
> I find DLS [1] to be very stable, updated more often [2], and it just works without issues (vs. Code-d)  ~~ at least for me. I think we should give it a chance.

I agree.

> I created a long list of features [3] I'd like to see in D IDE. Hopefully some of them is being worked on.

A list of features posted on wrong project page :)
Right link:
https://github.com/LaurentTreguier/dls/

Andrea

On Wednesday, 8 August 2018 at 20:56:51 UTC, tide wrote:
> On Wednesday, 8 August 2018 at 07:57:49 UTC, Laurent Tréguier wrote:
>> [...]
>
> Code-d overcomplicates things I find though. I can't even build it, there's so many dependencies attached to it that it isn't worth looking through to even find which one is causing the build issue. Let alone there's a restriction that it can only build 32-bit. Also can't be built with LDC2 cause of the dependencies is trying to build a 64-bit binary even though the arch is set to 32-bit. It's a mess. DLS took no time at all to build, nice and simple. Just one thing is installing the extension didn't create that symbolic link for me. And the plugin just silently passes an empty path if it can't find DLS.
>
> https://github.com/LaurentTreguier/vscode-dls/blob/master/src/extension.ts#L20

I've always had issues with Code-d! I filed several issues on its GitHub repo, but my experience with the Code-d author was that those issues are likely to remain open and unaddressed.

I switched to DLS and I'm much happier now. I'm glad we have options. So thanks for the hard work and keep it up!

On Thursday, 9 August 2018 at 10:37:32 UTC, IM wrote:
> I've always had issues with Code-d! I filed several issues on its GitHub repo, but my experience with the Code-d author was that those issues are likely to remain open and unaddressed.

Since he is a student (or at least he was some time ago, I don't know if it's still the case), he might simply have had little time to work on it, depending on the period of the year.

> I switched to DLS and I'm much happier now. I'm glad we have options. So thanks for the hard work and keep it up!

I'll try to keep it up :)

On Thursday, 9 August 2018 at 11:48:55 UTC, Laurent Tréguier wrote:
> On Thursday, 9 August 2018 at 10:37:32 UTC, IM wrote:
>> I've always had issues with Code-d! I filed several issues on its GitHub repo, but my experience with the Code-d author was that those issues are likely to remain open and unaddressed.
>
> Since he is a student (or at least he was some time ago, I don't know if it's still the case), he might simply have had little time to work on it, depending on the period of the year.
>
>> I switched to DLS and I'm much happier now. I'm glad we have options. So thanks for the hard work and keep it up!
>
> I'll try to keep it up :)

I just give it a try in visual studio code, but I got errors:

[Error - 20:39:54] Starting client failed
Error: Unsupported server configuration {
    "command": ""
}
	at _getServerWorkingDir.then.serverWorkingDir (C:\Users\Domain-Work\.vscode\extensions\laurenttreguier.vscode-dls-1.6.3\node_modules\vscode-languageclient\lib\main.js:356:35)
	at <anonymous>

On Thursday, 9 August 2018 at 12:42:45 UTC, Domain wrote:
> I just give it a try in visual studio code, but I got errors:
>
> [Error - 20:39:54] Starting client failed
> Error: Unsupported server configuration {
>     "command": ""
> }
> 	at _getServerWorkingDir.then.serverWorkingDir (C:\Users\Domain-Work\.vscode\extensions\laurenttreguier.vscode-dls-1.6.3\node_modules\vscode-languageclient\lib\main.js:356:35)
> 	at <anonymous>

Now that looks exactly like the bug I thought I had gotten rid of...
The bug was that on Windows, the bootstrap program could exit before the symbolic link to dls.exe was created, so the extension was left without anything to launch.

Does it continue like this after reloading VSCode's window ?

Creating symlinks requires admin rights on Windows. In order to do that I'm launching a powershell command to bring up the User Account Control popup.
I'm no Windows expert, so on some machines it could fail due to some strict policy about powershell execution, or simply not having the possibility to gain admin rights.
I was thinking about working around that problem in the next version; requiring admin rights for something like this is obviously not really optimal.

On Thursday, 9 August 2018 at 12:42:45 UTC, Domain wrote:
> I just give it a try in visual studio code, but I got errors:
>
> [Error - 20:39:54] Starting client failed
> Error: Unsupported server configuration {
>     "command": ""
> }
> 	at _getServerWorkingDir.then.serverWorkingDir (C:\Users\Domain-Work\.vscode\extensions\laurenttreguier.vscode-dls-1.6.3\node_modules\vscode-languageclient\lib\main.js:356:35)
> 	at <anonymous>

Do you have ldc.exe in your PATH by any chance ? I've just realized this can screw up everything; a patched version is on the way.

I really don't think we can call it "stable"...