It’s because the webinar is about Event Sourcing, and I find commands important. EventStoreDB is a database to store events. The ESDB client is a place where to store events, not an Event Sourcing library or framework.
I would expect others to disagree if the use MySQL or MongoDB 
It would be, indeed, nice to provide a sample with some database, although I am not yet sure what database it should be.
@raarts, thank you for your suggestions and frank opinion.
Regarding TS/JS and other technologies, we need to improve our diversity tho, in the last few months, I wrote a few articles with TS/NodeJS samples:
- https://www.eventstore.com/blog/how-to-get-the-current-entity-state-from-events
- https://www.eventstore.com/blog/snapshots-in-event-sourcing
- https://www.eventstore.com/blog/snapshotting-strategies
- https://www.eventstore.com/blog/keep-your-streams-short-temporal-modelling-for-fast-reads-and-optimal-data-retention
- https://www.eventstore.com/blog/nodejs-grpc-client-version-2.0.0-is-out
- https://www.eventstore.com/blog/nodejs-v1-release
You can also check my repository with NodeJS/TS samples: https://github.com/oskardudycz/EventSourcing.NodeJS/pull/14