I see what you mean.
Actually already watched it, was quite entertaining, though like I wrote a while back about it, the speaker sadly glossed over quite a few usability problems his example of a simpler solution for buying tickets created. Like the fact that if, like me or quite a lot of people, you don't own a credit card who's magnetic strip is activated you won't be able to use it at all.
The question though is, how we should tie KVM into the new design than. Because if it isn't used enough to even justify putting it on the download page for Linux, it will be used even less in the future, which in the end would mean that it'd be more efficient to drop support all together, if you understand what I'm saying.
Will look at it too. Personally enjoy reading research papers, etc. actually
That'd be a possible solution/path to go too.
That could be quite a good solution as well, though I feel like this could actually overwhelm new users more, as they'd be confused over the fact that seemingly the same thing has multiple different websites.
Personally, my idea/concept for a download page would contain something like this:
So, an easy to read, short comparison chart any user may understand. After all, arrow = good, no arrow = bad. Though again, such a chart could just as easily lead to more confusion, as people feel like only the "solution with the most arrows" is safe to use, which in turn would again alienate quite a lot of people.
I mean, to a certain extend, this can be seen with the current chart (Whonix vs Tails vs ...) already, as, at least from what I've seen, a lot of people who heard of Whonix somewhere go there, see how Tails is non persistent while Whonix is and feel that thus Tails is safer, because of their limited understanding of the subject matter.
However, at the same time, I see similar problems arrising with a more fragmented, multi site system. Maybe creating sub-homepages for each OS and/or hypervisor while keeping them all collected under the "whonix.org" domain might be a good solution. This again could however create confusion, as people might then see KVM-Whonix and VBox-Whonix as completley different "programs", which were soely developed by the same team and start to look for functional differences which by definition there aren't.
So, in conclusion, while I'm open for everything and feel like something needs to be done, I'm not entirely sure what it is that could be done, as all solutions I can think of have, at least from my point of view, quite big issues.
Have a nice day,