On Friday, 26 May 2017 at 16:55:44 UTC, Joakim wrote:
On Friday, 26 May 2017 at 11:32:21 UTC, Andrei Alexandrescu
Documentation of vibe.d was also mentioned as an important
problem. More precisely, it's the contrast between the quality
of the project and that of the documentation - someone said
his team ended up with a different (and arguably inferior)
product that was better documented. Literally they had the
same engineer try each for a day. Reportedly it was very
difficult to even figure whether vibe.d does some specific
thing, let alone tutorials and examples of how to do it.
Eh, documentation is going to be sparse for a non-corporate OSS
project. If they're building products with vibe.d, presumably
they can throw some consulting dollars Sonke's way and get him
A reasonable presumption, but I do not know if Sonke himself has
capacity for such as he seems quite busy.
So it might be worth thinking about alternative ways to move
towards better docs for vibe.d (in collaboration with Sonke).