Counterpoint: don't blame the founder for leading with driving use cases. It's audience selection bias, not the founder being reckless. He's showing what gets traction, not necessarily what he thinks people should actually do
I'm contributing to a similar open source coding tool [1] and I see the same skewed reaction: voice control of "whatever" while driving gets 5-10x the clicks of any other demo.
There's a logical reason so many people think of voice control while driving. It's not because they're reckless.
It reflects the hierarchy of needs. People with long commutes (often younger, lower-paid engineers living further out) spend 2+ hours driving daily.
This is their biggest time sink, so of course they think about making it productive. When you're living far out for cheap housing and hear "coding while driving", its easy to think: finally, a way to get ahead without choosing between career growth and seeing my family.
Again, I think its just an off-the-cuff reaction, not actually what people will do. Just like people try your app and tell you its amazing but then never pay. Doing stuff while driving just sounds nice until you know... you think about it for 3 seconds and yeah, its bad idea.
[1] https://github.com/slopus/happy