On Fri, 7 Oct 2016 21:40:32 +0200, Sönke Ludwig wrote:
Am 04.10.2016 um 22:34 schrieb Empty soul:
Vibe.d has a slow design process due to having to recompile everything when making even the minutest changes.
Is there a way, when a dt is changed to just recompile that dt without having to recompile the whole web server?
Not directly, but the latest RC (0.7.30-rc.1) can cache the compiled
Diet templates, which can speed up the compilation process considerably.
See
https://github.com/rejectedsoftware/diet-ng/#experimental-html-template-caching.
One thing that hopefully obsoletes this is the ongoing work in DMD's
CTFE interpreter, which is expected to bring huge compile-time improvements.There is also a [pull request][1] for DUB that adds a "watch" command,
which automatically rebuilds and restarts the application whenever a
source file changes. Together with the template caching and a permanent
session storage, this is almost as good as using an interpreted language.[1]: https://github.com/dlang/dub/pull/446
Ok, do you have any TOA for the watch command? I think the thing that is slowing dub down is checking for updates.
running dub stalls for a few seconds then shows
vibe-d:utils 0.7.29: target for configuration "library" is up to date.
vibe-d:data 0.7.29: target for configuration "library" is up to date.
vibe-d:core 0.7.29: target for configuration "libevent" is up to date.
vibe-d:http 0.7.29: target for configuration "library" is up to date.
vibe-d:diet 0.7.29: target for configuration "library" is up to date.
vibe-d:mail 0.7.29: target for configuration "library" is up to date.
vibe-d:mongodb 0.7.29: target for configuration "library" is up to date.
vibe-d:redis 0.7.29: target for configuration "library" is up to date.
vibe-d:web 0.7.29: target for configuration "library" is up to date.
vibe-d 0.7.29: target for configuration "libevent" is up to date.
Of course, I don't think it should check for updates all the time(once a week maybe?).