And I think he's heavily overrated because he presents well. For one thing, his basic premise is not really much different from Engelbart and Kay. For another

And I think he's heavily overrated because he presents well. For one thing, his basic premise is not really much different from Engelbart and Kay. For another, he doesn't propose specific processes or nuts and bolts design. The thinking trails off after "and then we make it more interactive..." Again, Engelbart did this. We've incorporated some pieces of it. We can still refine things. But the design problems always exist in the realm of compromise - if we automate more, we also have to specify more. General purpose solutions tend to fall back towards tried and true. When you put up a slick interactive demo, you have the benefit of being able to solve a very small problem, very precisely. You know what UX problem needs the most solving? Documentation. You made a thing to automate a thing. But you didn't document it. So it's too non obvious to bother with. So it doesn't get used. The best work that Victor, Case, et al have done is fundamentally a form of documentation, not expressive tools. I've seen lots of folks try to take the lesson to heart and make their app more like that documentation. But it's a mess because it tends to leave out some necessary level of power or performance to be a good tool. It's extremely expensive to add the interactivity in many real world cases.