Actually... I may have answered my own question in the OP. Most organisations already have a process for choosing what libraries they use (e.g. SpringMVC vs Struts or GWT)
What if the choice of language was on completely equal footing here? So whatever power developers have to influence and suggest the adoption of a library, they should be granted *exactly* the same means to influence the choice of language. As a rule-of-thumb it feels like it should adapt well to many firms. Could it possibly be that simple? -- Kevin Wright mail / gtalk / msn : [email protected] pulse / skype: kev.lee.wright twitter: @thecoda -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
