Yeah, chunk of simple text just specifically stating relevant information is easy to read, understand and even listen to using text-to-speech tools.
But also simple video of someone reading that chunk of text would produce transcript thats also easy to read.
But conversation in podcast like in T3 should be compared to messy text chat or forum conversation like in here.
If you compare the quality of podcast transcript to text-to-speech of this whole discussion here on forum you would find that both are not really good result.
So either both are discriminatory or neither is.
I would argue neither because doing podcast is not discriminatory against people that cant hear any more than writing here some info in text is to people that cant read.
The argument if some text forum posts would be better than podcast is different one. I am simply saying podcast is not discriminatory.
This actually made me laugh. We frequently talk about plans in our weekly podcast, we post links to the WiP source code changes so folks can see it being developed in real-time. Additionally we take questions from users and do our best to answer what we can when we can, usually within the very next episode.
Or maybe you mean, I should have personally flown out and given a conference talk on the planned changes, with mockups, diagrams, sample videos and demo systems at the ready. Or maybe that we should have our expensive engineers sitting around on the forums all day arguing with free users about every potential technical implementation detail vs actually getting work done to deliver on something? I’m sure THAT is a fantastic use of time, why didn’t we think about that before? Seriously, I think the expectations are way out of whack here.
All that said, this seems to have veered widely off topic, which was to get feedback on classic virtualization. I’m going to close it out now. The .2 is dropping soon anyway, so thank you to the folks who did give the nightly image a whirl and report feedback!