Why is Indigo such a hard sell to a lot of people ?
If you go to a set of presentations on Longhorn, people want to see the stuff about Avalon and Winfs but Indigo seems to a bit too theoretical for people and they are not sure why they would need it. Of course if you look at the very small proportion of the developer community who visit the PDC then they will soak it all up and say great that is what I need. Try and talk about it to a more general audience and you will get a bemused look.
I went to a presentation yesterday by a well known speaker who presented SOA and talked a little bit about Indigo. There were about 60 people in the audience, all of whom were architects for major companies in Switzerland. One reaction I heard was: isn't that stuff already in the framework ? Another comment was if this stuff already works why do I need something new. Ok, it might not be a clean unified model but I don't see why I need it.
People know there is plumbing in their houses but very few people get excited about it. All most people are interested in is that they get a hot shower or bath when they want one.
Maybe a better approach it show a real world problem where using Indigo makes development simpler. First explain the problem you are trying to solve in terms of a business case and then talk about the technology.
The problem is that people only use stuff if they know it exists and understand why to use it and what the benefits are.