Can vibe d leverage existing web technologies?

[sarn via Digitalmars-d-learn]

On Friday, 16 September 2016 at 12:46:34 UTC, Martin Tschierschke 
wrote:
> The "only" problem is you have to build your layout twice,
> in php and as diet template. :-(

You also have to manage URLs across different codebases.  I'd 
recommend against splitting up a frontend like that because it 
adds a lot of extra overhead.  But creating a new backend server 
isn't so expensive (not free, but not so expensive).  For 
example, I once wrote a thin proxy server in node.js for a 
third-party service that only supported node.js.  It wasn't as 
nice as a native solution would have been, but, hey, it worked.

Of course, with PHP it doesn't have to be a server.  A script 
might be simpler.