It's not my related to a lack of knowledge of the d-language but
the complexity of the vibe.d framework itself.
What I understand are :
1: jade/diet .dt templates, inheritance,includes,markdown.
2: A simple form with POST method.
Then it stops.
What I find too complex:
- Sessions, session data , session variables
- Handler functions and delegates, compile-time reflection,
prefixes, annotation.
- Authentication
- Validating user input
This can be improved by improving documentation in very small
steps.
As comparison here a tutorial of ruby-flask which uses only small
steps so everything can easily and completely be understood.
Something like that for vibe.d would be very interesting.
https://www.youtube.com/watch?v=3mwFC4SHY-Y
