critique of vibe.d

[Sean Kelly via Digitalmars-d]

On Wednesday, 9 July 2014 at 01:33:01 UTC, Puming wrote:
> Also, in playframework, vert.x and nodejs, they all have a 
> plugin/module system, that people could easily compose plugins 
> to make a website. (I call it plugin because that is what play 
> used to call it, now they all call it a module but that name 
> will easily conflict with D's sourcecode modules). This is a 
> critical mechanism that actually allured developers to 
> contribute to the eco-system.

On a related note, one thing vibe.d is really missing from my 
perspective is a good way to handle unstable processes and 
perform seamless code upgrades (this is where Erlang really 
shines IMO).  It would be cool if there were a process monitor at 
least.  The system I work with does some fancy stuff with UDS, 
but that probably isn't necessary.  I'll admit that the ball is 
probably kind of in my court here, since IPC would be a handy way 
of communicating process health, but something simpler using 
pipes or whatever would work as well.