I can't use nodejs anymore. Please vibe.d, don't follow that path

[Karabuta via Digitalmars-d]

On Friday, 21 October 2016 at 11:14:41 UTC, Sönke Ludwig wrote:
> Am 20.10.2016 um 22:25 schrieb Karabuta:
>> This is actually a nodejs project's dependencies for a small 
>> code-base.
>>
>> (...)
>>
>> Dependencies upon dependencies. Each package comes along with 
>> its own
>> dependencies. I give up nodejs, you win. Now I am investing my 
>> time in
>> Vibe.d which I hope ...
>
> I personally always try to minimize external dependencies, 
> because at some point they always cause problems. Sometimes 
> it's possible to resolve those quickly, but even then, it 
> usually leaves a bad taste if they are required for the whole 
> system to function reliably.
>
> On the other hand, my plan is definitely to split vibe.d itself 
> up into separate libraries, so that they can be maintained and 
> versioned according to their individual development pace. But 
> that means just that they are in separate repositories instead 
> of submodules within the same one, not finer granularity.

The thing about nodejs web frameworks is the usually lack of some 
basic functionality you would expect from say PHP without 
external libs. Little/single packages are more trouble, each with 
its own API design convention. Makes maintenance tedious. When 
one package dies out of support, problem comes: you have to find 
something else (which involves making huge code changes).