VSCode plugins

[Jerry via Digitalmars-d]

On Tuesday, 4 July 2017 at 06:26:52 UTC, Manu wrote:
> On 4 July 2017 at 14:59, bauss via Digitalmars-d < 
> digitalmars-d at puremagic.com> wrote:
>
>> On Tuesday, 4 July 2017 at 04:49:29 UTC, Manu wrote:
>>
>>> If authors of both plugins are active here, I ask; why have 2 
>>> separate
>>>
>>
>> The same reason there are multiple editors.
>>
>
> Errr. No.
> I don't think you can make an argument that one plugin performs 
> in a way
> that conforms to some peoples taste more than others... they do 
> exactly the
> same things, and even in the same way using the same tooling.
> There might be implementation quality differences, I don't 
> know, but that
> leads to the conclusion that merging them would produce the 
> best quality
> result.

Personally I use dlang-vscode because it doesn't tak on an extra 
process used for communication. I can understand wanting to put 
common code into one location so that multiple editors can reuse 
it, but ultimately you end up writing the same code for the 
editors anyways. Just now instead of communicating with 
DCD/DScanner/etc it is doing the same thing just communicating 
with this new process now. It's also really buggy and you don't 
get any information when something goes wrong. When it does go 
wrong in code-d, the workspace-d crashes and you now lose access 
to every feature. Where as in dlang-vscode if something goes 
wrong with DCD you still have access to features covered by the 
other processes. So they are different, and I do have my 
preference after using both of them.