Brian Palmer

That discussion doesn't give any details about how they did the benchmarks, so it's hard for me to comment -- all I can really say is the dinghy implementation of...

Yeah most of my projects these days are very small so I just haven't run into any performance blockers. I originally started the dinghy project back when I was working...

I've briefly considered it, as it'd make testing both vmware and virtualbox easier, but it's not a priority for me right now. I don't think using two different VMs day-to-day...

@saphiro Dinghy is basically in maintenance mode, as outlined in the README, I don't have plans to implement any new features. If anybody else wanted to take point here and...

Hi, can you provide more information on "dinghy is not available and does not work as expected"? What is not working, what are the symptoms, do you have any relevant...

@jimsimon That sounds like a docker-machine-driver-xhyve issue that I'm not going to be able to do anything about on the Dinghy side. Looking through that project I see [this issue](https://github.com/machine-drivers/docker-machine-driver-xhyve/issues/164)...

It's hard-coded right now, but I don't see any particular problem with adding support for `XDG_CONFIG_HOME` if you want to send over a PR. Right now `~/.dinghy` has both config...

Have you run into this again? Were both NFS processes the unfs3 daemon or was one system NFS?

Perhaps you've hit a state where the fsevents_to_vm daemon is still running but not functioning... do you see any relevant log output at `/usr/local/Cellar/dinghy/4.6.5/local/var/dinghy-FsEvents.output`?

That's expected that you won't see touched files in the log, fsevents_to_vm is silent by default and only prints touch events if you pass `--debug`. That's too bad that there's...