http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660This post strikes a chord with me. I sometimes find myself explaining to people that tech X, tech Y and tech Z all solve the same type of problem, so choosing between them is often down to the minutia (taste, particular requirements etc)". But, if someone has no experience with that *type* of technology, then they can't see the conceptual similarities between the derivatives. So they're stumped. For all they know, each technology gives something completely new and different, and picking one seems impossible. Innovation vs derivative is a nice way of putting it. It's more important to recognise that you actually *need* the the "innovation", rather than the particular derivative. http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment5http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment5Sun, 20 Jul 2008 23:02:16 GMTThe reason that I am saying Binsor led to innovation was that the power of scirpting language to configure the container has led me to creating rules to configure the containers, and that has affected the way I see working with the container. http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment4http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment4Sun, 20 Jul 2008 20:55:16 GMT"I seen the promo, but it has the same plot as all others, so I skipped it." That remind me the promo for ASP.NET 2: it was advertised as "write 70% less code" (hear 70% more tagsoup) and it was all about bland demo that has nothing to do with real world issue and was pushing the drag&dropers away from clean and nice design for the problem at hand (handling HTTP request and response in a maintainable way). I've never had to learn the new API upfront, concentrating over the features of the new backend languages and more interesting framework parts immediatly usefull That could stand true for many thing, I'm not jumping on or promoting a new thing unless there is a great probability it turns usefull for my projects and I've proved myself about this. Your counter example about Binsor (derivation leading to innovation) is more dual derivation to the wrap and extend features of container setup: - fluent interface and/or DSL - scripting enabled language it often takes more than one derivation to create something usefull and innovating, but there is nothing that mandate that such derivation must apply to the latest promoted framework, there is gap to fill all over our current base. What miss is out of the box thinking more than being accustomed with the latest to extend it first (there, you may come up with reimplementation of what is lacking from competing solution). http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment3http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment3Sun, 20 Jul 2008 20:37:15 GMTAnd the association to the topic at hand? http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment2http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment2Sun, 20 Jul 2008 18:09:20 GMTAyende, Hows the work on the book is going? http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment1http://ayende.com/3424/the-difference-between-derivation-and-innovation#comment1Sun, 20 Jul 2008 17:54:47 GMT